list_supported_languages

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

No annotations provided, but description accurately states it returns a table of codes. Simple read-only tool; no further behavioral traits needed.

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?

Two sentences, front-loaded with the main action, no extraneous words. Perfectly concise for a zero-parameter utility tool.

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?

Low complexity tool with no parameters and an output schema. Description fully explains purpose, usage context, and relation to sibling. No gaps.

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?

No parameters needed—schema is empty. Description adds value by explaining the codes' purpose (translation parameters), which is not apparent from schema alone.

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?

Clearly states the verb 'list' and resource 'language codes supported for translation'. Directly distinguishes from sibling translate_pdf by specifying that these codes are used as translation parameters.

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 that the returned codes can be used as lang_in or lang_out parameters, implying the tool should be called before translation. Lacks explicit when-not-to-use guidance but sufficient given one sibling.

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