get_translations

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

No annotations are provided so the description carries the full burden, and it delivers: it discloses the size cap, the truncated-slice-plus-note failure mode, and the correct recovery action rather than a retry. This is behavioral context well beyond what any schema could convey.

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 sentences, each earning its place, front-loaded with return shape and purpose before filters and the truncation caveat. No padding.

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?

Covers purpose, filter semantics, the duplicate-check workflow, and the truncation-failure recovery. With no output schema, the description still states the return structure, leaving nothing an agent needs to call it correctly 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 baseline is 3, but the description adds real meaning the schema lacks: glob applies to keys ('button.*') while substring applies to any locale value, and it clarifies the query's role as a truncation-avoidance lever.

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?

Specific verb+resource ('get all translations for a namespace') with the exact return shape stated. Distinguishes itself from siblings by naming get_namespace_keys and get_translation as narrower alternatives.

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?

States an explicit when-to-use rule ('Always call this before adding new keys to check for duplicates') and a when-not/recovery path ('narrow the query instead of retrying — or use get_namespace_keys and get_translation').

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