Generate text

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

Annotations are generic (no readOnly, etc.). Description adds that generating text costs credits ('Paid (a credit or two by length)'), which is useful behavioral info. Could mention idempotency or potential non-determinism but is generally good.

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?

Two succinct sentences. First sentence covers purpose and examples; second adds model details and cost. No redundancy. Front-loaded with key information.

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?

Given output schema exists and schema coverage is full, description covers purpose, usage boundaries, model selection, and cost. Complete for an AI agent to decide when and how to invoke.

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% (all parameters described). Description adds context: model is a writing-model id from hermoso_capabilities, and omitting it defaults to Claude orchestrator. This complements the schema.

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?

Description clearly states it generates raw text using writing models (Claude, Gemini, etc.) and lists specific use cases (ad copy, hooks, scripts). It distinguishes from sibling tools like plan_ad and render_ad that handle ad assembly.

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?

Explicitly says 'prompt-only, no ad assembly' and directs users to plan_ad and render_ad for finished on-brand creatives. Also explains model parameter usage and default behavior.

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