lokalise_delete_glossary_terms

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

No annotations provided, but the description discloses that the tool deletes all term translations and rules, and supports bulk deletion. It doesn't cover permissions or rate limits, but for a delete operation this is adequate.

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?

Five short sentences, front-loaded with purpose. Every sentence adds value: purpose, required params, use cases, return, warning, and alternative. Minimal waste.

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 output schema, the description includes return type ('Deletion confirmation'). Covers purpose, usage, warnings, and alternatives. For a simple delete tool with two parameters, it's sufficiently complete.

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% and both parameters are described. The description adds value by stating that termIds supports bulk deletion (array of numbers) and reinforces requirement. Provides context beyond schema without duplication.

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 'Removes obsolete or incorrect glossary entries' with specific verb and resource. It lists required parameters and mentions deletion. However, it doesn't explicitly differentiate from sibling tools like 'lokalise_update_glossary_terms', though the alternative is hinted.

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 ('clean up outdated terminology, remove duplicates, or fix mistakes') and provides a caution ('Consider updating instead of deleting for audit trail'). Also notes bulk deletion support and warns about removing translations and rules.

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