Delete Collection Comment

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds the crucial 'Cannot be undone' warning and notes it operates via a web session, which is useful behavioral context beyond the annotations. No contradiction with annotations.

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?

Two short sentences with zero waste. The core action is front-loaded, and the irreversibility warning is included without padding.

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 single-parameter destructive tool with annotations covering idempotency and destructiveness, the description is nearly complete. It could mention what happens to the comment (e.g., whether it disappears for others immediately), but the 'Cannot be undone' warning covers the essential risk.

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 description coverage is 0%, so the description carries the burden. The description doesn't explain what comment_id refers to beyond the obvious, but with a single required parameter named comment_id, the meaning is largely self-evident. The description adds no extra detail about the parameter format or source.

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 a specific verb ('Delete (discard)'), a specific resource ('your collection comment'), and even names the underlying mutation ('DiscardComment mutation via web session'). It clearly distinguishes from siblings like edit_collection_comment and post_collection_comment.

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 makes clear this deletes the user's own collection comment, which implies it is for comments the user authored. It doesn't explicitly name alternatives or exclusions, but the scope ('your collection comment') provides clear context for when to use it versus other comment tools.

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