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

Goes well beyond the annotations by disclosing privacy (own Argos Translate server, no third party), the truncation behavior for long text, the English-pivot fallback for indirect pairs, and the pricing/payment mechanics ($0.009 USDC per call via x402 on four chains). This is exactly the extra context annotations can't carry.

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?

Front-loaded with the core action and supported languages, then layers privacy, limits, routing, price, and a runnable sample. Dense but every clause carries operative information; the language enumeration is long but necessary for correct target_lang selection.

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 a stateless translation call with no output schema, the description covers inputs, limits, fallback behavior, payment requirements, and provides a free-sample invocation. Nothing an agent needs to call it correctly is missing.

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%, so the schema already documents text, source_lang, and target_lang. The description adds the max-length constraint and auto-detect default (both already in the schema) and mentions 'confidence' even though no such parameter exists in the schema, adding little clear value over structured fields.

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 precise verb+resource ('Translate text between 21 languages'), enumerates the supported language codes, and is clearly distinguishable from neighbors like language_detect or tts. An agent knows exactly what this does and its scope without opening the schema.

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?

Explains operating context well: 1000-char limit, source_lang auto-detect default, and that indirect pairs route through English. It doesn't explicitly name an alternative tool (e.g., language_detect for detection-only) or state when-not-to-use, so it stops short of full routing guidance.

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