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

The annotations already indicate read-only, idempotent, open-world, and non-destructive behavior. The description adds valuable behavioral details beyond that: 'Preserves JSON structure, keys, and non-string values' and 'Auto-chunks large payloads.' These are not encoded in the annotations and help the agent predict how the tool operates. No contradictions with 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?

The description is three sentences long, front-loaded with the primary action, and every sentence adds value: what it does, key behaviors, and a typical use case. No filler or redundant phrasing. It is appropriately sized for the tool's complexity.

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 presence of a thorough input schema, a rich set of annotations (readOnly, idempotent, openWorld), and a declared output schema, the description is complete for the tool's purpose. It covers the operational essentials (translation scope, structure preservation, chunking) and leaves structured details to the schemas.

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?

The input schema covers 100% of parameters with descriptive text for each. The tool description does not repeat or enhance those parameter details, but schema descriptions already define each parameter fully. Baseline 3 is appropriate since the schema carries the parameter documentation burden.

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 a specific verb and resource: 'Translate all string values in a JSON object or array to any target language.' It clearly states what the tool does, distinguishes it from sibling tools (none of which handle translation), and highlights scope (bulk JSON translation). This is unambiguous and specific.

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 an explicit use case ('Ideal for i18n locale files'), which gives contextual guidance on when to apply the tool. However, it does not explicitly mention alternatives or exclusions, though the sibling tool names make the differentiation fairly obvious. Clear context is present, but no when-not-to-use guidance is given.

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