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

Annotations already declare readOnly=false, destructive=false and idempotent=false, so the safety profile is covered. The description adds a genuinely non-obvious behavioral trait: the collection id is derived from the title and becomes the first segment of article slugs, which has real consequences for later article URLs. It does not address permissions or visibility defaults, so it stops short of a 5.

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?

A single dense sentence that front-loads the action, then the accepted fields, then the ordering constraint and the id-derivation rule. Nothing is padded and nothing is repeated from the structured fields.

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?

For a creation tool the description covers purpose, fields and the slug/id rule, and with no output schema it need not explain returns. However it omits the required productId linkage and whether the new collection is immediately live versus draft, leaving gaps an agent would want before creating one.

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 every parameter is already documented in the schema and the baseline is 3. The description names title, description and icon but adds no meaning for productId or the visibility enum beyond what the schema states.

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 ('Start a new collection in the help center') and immediately scopes it with the fields it accepts and the ordering constraint ('before any article is filed in it'). An agent can distinguish this from update_collection or create_article without opening any schema.

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?

The phrase 'before any article is filed in it' implies the sequencing use case, but the description never names alternatives (create_product, update_collection) or states when a collection is the right container versus, say, a product. Usage is inferable rather than explicit.

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