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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral details: 'Preserves JSON structure, keys, and non-string values. Auto-chunks large payloads.' It does not contradict annotations, and adds context beyond what annotations provide.

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 extremely concise (3 sentences) and front-loads the core action. Every sentence serves a purpose: stating what it does, how it behaves, and when to use it. No wasted 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 rich input schema (100% parameter coverage) and presence of an output schema, the description provides sufficient context: purpose, behavioral traits, and use case. An agent can confidently decide when to invoke this tool.

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?

All 4 parameters are fully described in the input schema (100% coverage). The description adds value by explaining overall behavior (auto-chunking, preservation of structure) and the intended use case (i18n files), complementing the schema's detailed per-parameter 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 clearly states the tool's purpose: 'Translate all string values in a JSON object or array to any target language.' It specifies the verb (translate) and resource (JSON strings), and distinguishes itself from sibling tools (e.g., analyze_document, extract_web) which are unrelated to translation.

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 explicitly states the ideal use case: 'Ideal for i18n locale files.' This provides clear context for when to use the tool. However, it does not mention when not to use it or provide alternatives among siblings, which would improve the score to 5.

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