keys

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

No annotations are provided, so the description carries the full transparency burden. It states it lists key paths and can filter, but it does not disclose pagination behavior, default limits, or explicitly state that it is a read-only operation. This is minimal for a list tool and does not add context beyond what the schema already provides.

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 a single sentence, front-loaded with the action ('List translation key paths'), and includes the key filtering capability with no superfluous words. It is concise and well-structured.

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?

The tool is simple with optional filters, and the description covers the primary use case. However, with no output schema or annotations, it does not explain return format, default behaviors, or edge cases. It is adequate but not fully complete for an agent that might need more context on what the tool returns or how it behaves.

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 schema covers all three parameters (limit, locale, prefix) with descriptions, so the baseline is 3. The description adds that locale and prefix are filters, but this is already implied by the schema's parameter descriptions. No new semantic meaning is provided 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?

The description uses the specific verb 'List' and clearly identifies the resource as 'translation key paths'. It also mentions filtering by locale and/or prefix, which distinguishes it from sibling tools like get_key (single key) and search (likely more complex). The purpose is unambiguous and directly actionable.

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 gives clear context for when to use this tool (listing translation key paths, optionally filtered), but it does not explicitly contrast with alternatives such as search or get_key. There is no when-not-to-use guidance or mention of alternative tools, leaving usage somewhat implied.

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