get_all_translation_keys

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value by clarifying the exact return content ('key and namespace only'), which is not obvious from the tool name alone. It does not discuss pagination or limits, but for a no-parameter read-only tool the provided context is sufficient.

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 extremely concise: one sentence states the core function, one confirms no parameters, and one states the intended use case. Every sentence earns its place and is front-loaded with the most important detail.

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, no-parameter, read-only list tool, the description is complete. It tells the agent what will be returned, what is excluded, and when to use it. No output schema exists, but the return content is described well enough for correct invocation and expectation-setting.

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 tool has zero parameters, so the description's statement 'No parameters required' adds minimal information beyond the empty input schema. Per the baseline for zero-parameter tools, this is adequate and no further parameter detail is needed.

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 states a specific verb ('return'), the resource ('all translation keys'), and the exact scope ('key and namespace only') in your SimpleLocalize project. This makes it clear what the tool does and distinguishes it from translation detail or mutation 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?

The description gives a clear use case: 'Use this to quickly fetch all keys for reference or validation.' It does not explicitly name alternatives or exclusion conditions, but the usage context is specific enough for an agent to select it appropriately.

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