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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful context beyond those: 'Stateless', 'No local context is used', and 'Paid per call' (cost implication). This gives the agent useful behavioral expectations without contradicting the annotations.

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 crisp sentences, each carrying distinct information: stateless API type, scope of translation, absence of local context, and billing. The description is front-loaded and contains no filler or redundant restatement of the tool name.

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 two-parameter, stateless translation API, the description covers the critical operational facts: scope, statelessness, billing, and target language. It doesn't mention return format, but with no output schema and a self-evident translation result, that gap is acceptable. Sibling differentiation is implicit rather than explicit.

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 the baseline of 3 applies. The description loosely aligns with the parameters ('provided text' and 'target language') but introduces no additional parameter-level nuances beyond what the schema already documents.

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 states exactly what the tool does: 'Translates ONLY the provided text into the target language.' It identifies a specific verb (translates), a resource (provided text), and a target (target language). The 'Stateless' qualifier and 'ONLY' scope help differentiate it from context-aware siblings like paid_llm_route or paid_convert.

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 conveys a clear usage context—stateless translation of a single text—and implies it is not for context-sensitive tasks. However, it never explicitly names alternative tools or gives when-not-to-use guidance, leaving the agent to infer routing from the stateless/context-free clues.

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