delete_translation_key

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

Annotations already carry the destructiveHint=true and idempotentHint=false, so the risky nature of the operation is covered. The description adds the scope ('single translation key') but does not mention consequences like cascade deletion or irreversibility. This is acceptable but not rich.

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 compact and front-loaded: the main action is in the first sentence, followed by direct parameter guidance and an alternative. Every sentence earns its place with no fluff.

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 deletion tool, the description, schema, and annotations together cover the essential invocation details: parameters, required fields, destructiveness, and the bulk alternative. A mention of what happens after deletion or return value would be nice, but it is not necessary for correct tool selection and invocation.

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%, so both 'key' and 'namespace' are already documented. The description only restates that 'key' is required and 'namespace' is optional, which adds no new semantic depth 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 clearly states the specific verb ('delete') and resource ('a single translation key') and ties it to the SimpleLocalize project. It also explicitly distinguishes itself from delete_translation_keys_bulk by framing the bulk tool as the alternative for multiple keys.

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 provides explicit guidance: it explains the required 'key' and optional 'namespace', and clearly states when to use the sibling bulk tool instead. This gives an agent a direct routing rule for single vs. multiple deletion.

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