lokalise_delete_comment

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

Clearly states permanence ('cannot be undone') and includes a warning and consideration to archive discussions. Since no annotations exist, the description fully covers destructive nature and return value ('Confirmation of deletion').

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?

Description is structured with clear sections (purpose, required params, use cases, return, warning) but is slightly verbose with five sentences. Still, it is front-loaded with the primary action.

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 delete operation with three required parameters and no output schema, the description provides comprehensive context: purpose, required IDs, use cases, return type, and irreversible consequence.

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?

Input schema covers all three parameters with descriptions (100% coverage). Description redundantly lists required parameters but adds no additional semantic detail 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 verb 'removes' and the resource 'specific comment from a translation key', distinguishing it from other delete tools (e.g., delete_key, delete_project) by specifying the context of comments.

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?

Provides explicit use cases: 'clean up resolved discussions, remove outdated information, or delete accidental comments'. However, it does not mention when not to use or suggest alternatives like get_comment or list_comments.

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