Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description does real work: it discloses the cost profile ('Free — costs 0 credits') and the key lifecycle distinction that smart collections are resolved on-demand rather than materialized. It omits failure modes such as duplicate-name behavior and whether type is immutable after creation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, zero filler. The core action leads, the mode branch follows, and the cost note is a short trailing clause that carries real decision value (credits are a tracked concern in this toolset).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers creation semantics, mode selection, predicate syntax, and cost for a 4-parameter tool with a nested object. The notable gap is that no output schema exists, yet the description never says what comes back (e.g. a collection id needed for add_to_collection or resolve_collection).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns more by instantiating the opaque config object with a concrete predicate ({format:'video',min_likes:50}) and restating that config is required for smart collections. It adds no meaning for name or description, which the schema already covers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a new post collection') and immediately scopes it to the authenticated user. It also distinguishes the two creation modes and names the sibling tools (add_to_collection, resolve_collection) that operate on the result, so an agent can place it precisely in the collection family.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear branching guidance: use type='manual' when you intend to hand-curate via add_to_collection, use type='smart' with a config predicate for a dynamic collection. It stops short of stating exclusions, e.g. checking list_collections first or that type cannot be changed later, but the when-to-use path is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.