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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, so the bar for additional disclosure is lower. The description adds the return semantics (a key-to-letter map), which is useful, but says nothing about format, size, language coverage, or error behavior.

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 core return value followed by use cases; little waste. The phrasing 'for transliterate' is slightly awkward for 'for transliteration', but the structure remains clear and efficient.

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 simple read-only lookup with rich schema and annotation coverage, the description adequately explains what the tool returns. It could be more complete by hinting at the output format (e.g., object vs. list) since no output schema exists, but the core information is present.

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% and the single language parameter is already documented as accepting codes or names. The description only restates 'for a language' and adds no syntax, examples, or constraints beyond the schema.

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?

States a specific verb (returns) and resource (phonetic keyboard map for a language), and describes the content (Latin keys → letters). It also names the sibling transliterate and positions itself as an input-building helper, giving an agent enough to distinguish it from the conversion tools.

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?

Provides two clear use cases: teaching typing and building romanised input for transliterate. It does not state when not to use it or explicitly compare against convert_script/list_languages/native_digits, but the context is sufficient to guide selection.

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