sw_delete_comment

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

Annotations only declare destructiveHint. The description adds critical behavioral context: without confirm:true it is a dry-run with NO network call, and with confirm:true it actually deletes. This significantly clarifies the tool's safety profile and goes beyond what annotations provide.

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 two sentences, front-loaded with the core action, and every word earns its place. It is concise without sacrificing essential safety information.

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 simple two-parameter deletion tool with no output schema, the description is complete. It explains the destructive action, the dry-run behavior, and the confirm requirement. No critical missing information.

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 already describes both parameters (id, confirm) with 100% coverage. The description reinforces the relationship between confirm and execution, and adds the 'NO network call' nuance not present in the schema. This adds value beyond the schema's individual parameter descriptions.

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 tool's function: 'Delete a comment by id.' The verb is specific and the resource is unambiguous. It also distinguishes from sibling delete tools (group, friend, expense) by naming 'comment' explicitly.

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 provides clear operational context: the tool is for deleting a comment, and the confirm flag controls dry-run vs actual deletion. It does not explicitly discuss when to use this over alternatives, but the purpose is so specific that usage is implied. A 5 would require named exclusions or alternative comparisons.

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