Delete a comment (irreversible)

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

While annotations already declare destructiveHint=true, the description adds crucial context: 'IRREVERSIBLE' and 'Requires confirmation.' It also clarifies scope to 'your comments,' preventing accidental deletion of others' content. This goes beyond what annotations provide, though it doesn't detail the two-step confirmation process.

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?

The description is composed of three short, front-loaded statements: 'IRREVERSIBLE,' 'Deletes one of your comments,' and 'Requires confirmation.' Every word earns its place, with the most critical warning stated first.

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 destructive deletion tool, the description covers the essential points: irreversibility, ownership, and confirmation. The schema's confirmation_token description fills in the two-step process, and annotations convey the destructive nature. It lacks explicit return value details, but that is not expected given the absence of an output schema.

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?

The description provides no parameter-specific guidance. The schema covers confirmation_token thoroughly but leaves comment_id undocumented (50% schema coverage). The description does not compensate for this gap, offering only 'your comments' as a marginal hint toward comment_id's meaning.

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 action ('Deletes') and the resource ('one of your comments'), which is specific and differentiates it from sibling tools like delete_list or delete_playthrough. The title reinforces this with 'Delete a comment (irreversible).' This is not a tautology.

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?

The description does not explicitly say when to use this tool versus alternatives, but the phrase 'Deletes one of your comments' implies it is for removing your own comments. 'Requires confirmation' hints at the required flow. However, no exclusions or alternative tools are mentioned, so guidance is implied rather than explicit.

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