delete_translation_keys_bulk

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

Annotations already flag destructiveHint=true and idempotentHint=false. The description adds useful behavioral detail beyond that: missing keys do not cause an error, and the tool returns a failures list when applicable. This meaningfully sets expectations for a destructive bulk operation.

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 with the action and resource. The three bullet points each earn their place: input shape, error behavior, and recommended use case. There is almost no filler.

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 one-parameter destructive tool with no output schema, the description covers what to pass, the size limits, behavior for nonexistent keys, the failure-list response signal, and when to use the tool. It leaves the failure-list structure unspecified, but that is a minor gap.

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 input schema already documents the translationKeys array, min/max items, and the key/namespace properties. The description essentially restates these facts without adding extra semantics or edge-case guidance. With 100% schema coverage, baseline 3 is appropriate.

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 the specific verb 'delete', the resource 'translation keys', and the scope 'in bulk in your SimpleLocalize project'. The word 'bulk' distinguishes this tool from the singular sibling delete_translation_key without needing to open the schema.

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?

It gives a clear usage context: 'Use this to clean up unused keys efficiently.' This tells an agent when the tool is appropriate. It does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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