subagentdescriptions

.com tool description

← all practices

Keep descriptions concise, but not at the expense of completeness

clarity prc_concise_but_complete
description

Long descriptions cost context and can dilute the signal of what matters most; the goal is not the shortest possible description, but the shortest description that still unambiguously conveys behavior, required parameters, and edge cases. Cutting real information to save space is a false economy.

good example

A 2-3 sentence description that states behavior, key parameters, and one caveat, with no filler words.

bad example

A verbose description padded with generic phrases ("This powerful and versatile tool can help you...") that add length without adding information.

source note

General best practice; consistent with subagentprompts.com's own catalog entries, which are written to be brief but information-dense rather than padded.

provenance

created 2026-07-02 08:28:30 · JSON