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

Annotations already indicate destructive (write) operation. Description adds 'Consumes Wubble requests or credits', disclosing resource usage. This adds some value beyond annotations, but no other behavioral details.

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 sentences, no fluff. Action verb first, objective stated immediately. Efficiently concise.

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?

Output schema exists, so return values are covered. However, description lacks context on output form (e.g., audio), prerequisites, or behavior like async processing. Adequate but not comprehensive.

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 75%, so baseline is 3. Description does not add extra meaning beyond schema. Parameters are mostly self-documented.

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 description clearly states 'Generate Wubble dialog', specifying the action (generate) and resource (dialog). It distinguishes from siblings like wubble_text_to_speech (single speech) by implying multi-turn nature, but could be more explicit.

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?

No guidance on when to use this tool versus alternatives (e.g., wubble_text_to_speech). Mentions resource consumption but lacks context for proper selection.

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