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

The description reveals behavioral traits beyond annotations: 'Fast cheap LLM under the hood; the x402 payment IS the auth. ($0.01 per call, paid via x402)' This adds transparency about cost and authentication. Also mentions character limit and preservation of formatting, code, etc.

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?

The description is concise with three sentences. The first sentence front-loads the core purpose, the second covers constraints and examples, and the third adds optionality and cost. No unnecessary words.

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 the tool has an output schema (thus return values are covered) and the description covers purpose, parameters, limitations, cost, and authentication, it is fully complete for an agent to select and invoke correctly.

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%, but description adds significant value by providing examples for target ('spanish', 'de', 'ja'), specifying the character limit for text, and explaining optional parameters (source, formality). This goes beyond the schema's descriptions.

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 starts with 'TRANSLATION' and clearly states the action: POST text and target to get translation plus detected source language. It distinguishes itself from sibling tools by being the only translation tool among many post_* tools.

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 description provides explicit guidance on how to use the tool: any language pair, target as name or ISO code, examples given. It does not explicitly state when not to use it, but the context of a single translation tool makes it clear.

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