lokalise_delete_key

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

No annotations, so description fully covers behavior: 'Permanently removes', 'Irreversible – all translations lost', returns confirmation. Discloses destructive nature and required parameters.

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, front-loaded with purpose and requirements. Each sentence adds value: purpose, use case, warning, alternative. Slightly verbose but efficient.

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?

No output schema, but description mentions return value. Covers all necessary context: irreversibility, parameter requirements, use cases, alternative for multiple keys. Complete for a simple delete tool.

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 covers 100% of parameters. Description restates required params but adds no additional semantic meaning beyond what schema already provides. Adequate but not extra.

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?

Clear verb ('removes') + resource ('obsolete content and all its translations'). Distinguishes from sibling 'bulk delete' by explicitly mentioning it for multiple keys. Use cases provided.

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 (removing deprecated features, cleaning typos) and when not (multiple keys – use bulk delete). Includes warning about irreversibility and suggestion to archive.

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