Delete Comment Tool

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

Goes beyond destructiveHint=true by stating irreversibility explicitly ('It cannot be undone') and disclosing a permission nuance the annotation cannot convey: an admin can delete anyone's comment on an update, while otherwise only the person's own comment is deletable. Failure behavior (e.g., comment not found) is not covered, keeping it short of a 5.

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, none wasted, with the destructive action and its condition front-loaded. The nested parentheticals around the 'on' values make it slightly dense to parse but nothing is redundant.

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?

With no output schema needed and full schema coverage, the description supplies the mutation semantics, irreversibility, ownership rules, and id provenance an agent needs to call this safely. Only the result/error shape is unaddressed.

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 the baseline is 3; the description adds real value by explaining where the 'id' originates and by tying the 'on' enum values to their behavioral difference (task = own only, update = admin can delete anyone's). The 'session' parameter is still left to 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?

States a specific verb and resource (deletes a comment) plus scope: only the person's own comments, on a task or an update, with the admin exception for updates. This is precise enough to distinguish it from comment_update/add_note siblings without opening any schema.

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?

Gives an explicit gating condition ('only when the person asks, after telling them which comment it is') and explains where to obtain the id (start_task, list_tasks, project_timeline, last_update, with 'mine' marking ownership). Both when-to-use and the prerequisite lookup path are spelled out.

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