Delete Comment

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description's 'This is destructive' is largely redundant, but it adds real nuance by scoping the damage ('for that comment') rather than the whole thread, which the annotations cannot express. It leaves open what happens to threaded replies, so not a full 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?

Two short clauses, zero waste, with the action stated first and the disambiguation second — front-loaded exactly as it should be.

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?

Output schema exists and annotations cover safety and idempotency, so the definition is nearly complete for a one-parameter delete; the only missing piece is whether deleting a parent comment cascades to its replies, which matters for a destructive open-world operation.

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 100% and the id parameter is already documented as coming from list_comments/create_comment; the description's 'by id' adds no syntax, format, or sourcing detail beyond that. Baseline 3 applies.

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 ('Delete an existing comment by id') and immediately contrasts with the sibling resolve_comment, so it is distinguishable from update_comment/resolve_comment without opening a 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?

Explicitly names the alternative (resolve_comment) and the condition that selects it ('when you only want to mark a thread resolved'), which is exactly the decision boundary an agent needs for this cluster of comment tools.

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