Delete a Reddit post

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

Annotations already mark destructiveHint and readOnlyHint=false, but the description goes far beyond by explaining that Reddit's delete endpoint returns empty success even for unauthorized posts, that the verdict must come from re-reading the post, and that comments persist. This adds substantial behavioral context not present in 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?

The description is lengthy, but every sentence conveys essential safety or workflow information. It is heavily front-loaded with the permanent deletion warning and the confirm-first instruction. Slightly verbose, but justified given destructive consequences.

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?

Covers the full destructive operation: two-call flow, confirmName logic, comment persistence, empty-success behavior, credit cost, and connection requirement. No additional information an agent needs is missing, despite the absence of an output schema.

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?

Although schema coverage is 100%, the description adds critical semantic value: it explains that confirmName becomes required once the post has comments or a real score, and clarifies the exact title matching requirement. This is essential for correct invocation that the schema alone does not convey.

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 the verb (delete) and specific resource (a Reddit post), and is distinct from other delete_* siblings. The description fully clarifies what is being operated on and the permanent nature of the action.

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?

Provides a precise two-step usage protocol: call without confirm first, show the user the post details, get unambiguous consent, then call again with confirm:true and confirmName. Also notes the prerequisite of Reddit being connected, making it explicit when to use this tool.

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