delete_comment

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

No annotations are provided, so the description carries the full burden. It explicitly states the action is permanent and irreversible, which are critical behavioral traits for a deletion tool. It does not cover authorization specifics or rate limits, but the core behavior is disclosed.

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 a single focused sentence that begins with the key action. It is concise and front-loaded, but could be improved by including brief parameter guidance without adding much length.

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 deletion tool, the description covers the main behavioral trait (irreversibility) and ownership. However, it lacks information about error conditions, output (though an output schema exists), and does not explain parameters, leaving some gaps in completeness.

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 coverage is 0%, and the description does not mention or explain the parameters (comment_id and optional account). While parameter names are somewhat self-explanatory, the description fails to add value beyond the schema, such as clarifying the purpose of the optional account parameter.

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 purpose: 'Permanently delete a comment you own (or a comment on your media). Irreversible.' It specifies the verb (delete), resource (comment), and ownership conditions. This distinguishes it from sibling tools like hide_comment or get_comments.

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 context on when to use the tool (comments you own or on your media) and implies irreversibility. However, it does not explicitly mention when not to use it or alternative approaches like hiding instead of deleting.

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