Delete a comment on a forum thread

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

The description adds valuable context beyond the annotations: login requirement, ownership constraint, irreversibility, and non-idempotent error behavior. This fully discloses the behavioral profile of the tool.

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?

A single, well-structured sentence conveys all essential information: requirement, action, ownership, ID source, and caveats. No filler words, with important caveats placed at the end.

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 delete operation with one parameter, the description covers prerequisites, ownership, reversibility, and error behavior. Combined with the output schema and annotations, it is fully complete for an agent to invoke confidently.

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 schema already describes the id parameter, but the description adds crucial sourcing information (where to obtain the ID) and clarifies that it's the comment owner's ID. This goes beyond what the schema provides.

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 uses the specific verb 'Delete' with the resource 'comment' and states the ownership requirement, clearly distinguishing it from sibling tools like delete_thread and delete_activity. The mention of ID sources (get_thread_comments, post_thread_comment) further clarifies the target.

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?

It explicitly states the prerequisite of login and ownership, and explains what happens on repeated calls. While it doesn't name explicit alternatives, the context (delete a comment vs. a thread) is clear enough for an agent to choose correctly.

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