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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'Read only' merely repeats structured data. The one piece of added context is that draft generation is bundled with a search, which is useful cost behavior but stated too vaguely to rely on.

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 short sentences with the purpose front-loaded and no filler. The middle sentence is terse to the point of ambiguity, but nothing is wasted.

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?

With no parameters and full annotations, little is required, but the description never says what a 'quote' returns (cost, credits, availability) or how it relates to the pitch lifecycle, and there is no output schema to fill that gap.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the empty schema and full coverage leave no semantic gap.

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?

The verb+resource pair 'Quote a pitch draft' identifies the object but leaves the meaning of 'quote' (price/cost estimate versus textual quotation) to inference from the many sibling *_quote tools. It does not distinguish this from soclo_creators_pitch or soclo_creators_search_quote.

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?

'Drafts are included with a search' hints at an alternative path (search) that may make a separate quote unnecessary, but the implication is oblique and never states when to call this tool versus soclo_creators_pitch or soclo_creators_search_quote.

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