lokalise_delete_task

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

Discloses key behavior: 'Only removes the assignment - keys and translations remain unchanged' and 'Cannot be undone.' Since no annotations exist, this context is valuable. No mention of auth or rate limits, but sufficient for a delete 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?

Three concise sentences covering purpose, usage, return, and a note. No wasted words, well-structured.

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?

Adequately covers purpose, usage, behavioral impact, and return value for a simple two-parameter tool. Could mention potential errors or who can cancel, but not essential.

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?

Parameters are fully described in the schema (100% coverage). Description adds no extra meaning beyond listing required parameters. 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?

Description clearly states 'Cancels a work assignment, removing it from assignee queues,' with a specific verb and resource. It distinguishes from other delete tools (e.g., delete key, delete comment) by focusing on tasks.

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: 'Use to cancel mistaken tasks, clean completed work, or remove test assignments.' However, it does not mention when not to use or alternatives like updating a task.

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