lokalise_bulk_delete_keys

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

With no annotations, the description covers irreversibility, permanent deletion of keys and translations, and mentions the return type. Could be slightly more specific on result details, but 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?

Three sentences total: purpose, required params, use cases, return, and warning. Every sentence is necessary and front-loaded. No wasted words.

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?

Given no annotations and no output schema, the description covers all essential aspects: purpose, when to use, required params, irreversibility, and return type. Complete for the tool's simplicity.

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 coverage is 100%, so schema already documents parameters. Description repeats 'Required: projectId, keyIds array' but adds no new meaning beyond schema. Baseline 3.

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?

Clearly states the tool's purpose: 'Large-scale cleanup removing multiple obsolete keys permanently.' Distinguishes from siblings like lokalise_delete_key (single key) and bulk_update_keys (update vs delete).

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?

Explicitly states when to use: 'For removing deprecated feature sets, post-refactoring cleanup, or major content pruning.' Provides critical warning about irreversibility and advises verifying key list.

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