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

Goes well beyond the annotations: discloses that calls are metered against plan credits, non-idempotent in a costly way ('every call generates and charges again'), asynchronous with sub-minute latency, and that output persists to Ghostwriter history visible in the dashboard. It also clarifies org scoping and that no accountId is required — none of which the annotation block conveys.

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?

Four sentences, front-loaded with what it does, then when to use it, then the operational constraints that most affect a wrong call (cost, async polling), then the negative scope. Each sentence carries distinct information with no repetition.

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 an async, metered generation tool this covers everything an agent needs: cost model, latency, the returned generation id plus the sibling to poll, org scoping, and output persistence. Return shape is handled by the existing output schema, so no gap remains.

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 description coverage is 100%, so topic, cta, keywords, contentType, and priorOutputs are already fully documented in structured form. The description adds only the org-scoping fact ('no accountId needed') rather than any parameter mechanics, so the baseline 3 applies.

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 — writes Pin titles and descriptions via Tailwind's Ghostwriter — and explicitly bounds scope: 'Pinterest Pin copy only; it does not write blog posts, emails, or product listings.' That exclusion plus the named polling sibling makes it unmistakable against neighbors like generate_pins_from_url or regenerate_pin_design.

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 an explicit trigger ('when the user asks for Tailwind or Ghostwriter to write their Pin copy, or for copy in their saved brand voice') and an explicit anti-pattern ('poll the id you have rather than re-calling'), naming get_copy_generation_status as the alternative. Nothing is left to inference.

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