Delete a post

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

Adds 'permanent' behavior beyond the destructiveHint annotation. Also clarifies ownership constraint (your own posts) not captured by 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?

Two sentences, front-loaded with action and constraint. No unnecessary words.

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 ownership constraint, permanence, and parameter alternatives. No output schema needed; return behavior is obvious for a delete 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 covers all three parameters with descriptions. Description adds that parameters are alternative methods (url or handle+code), but this is already implied by schema structure.

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?

Specifically states 'Delete one of YOUR OWN Threads posts' with clear verb and resource. Distinguishes from sibling tools like 'unlike_thread' or 'unrepost_thread' which are different actions.

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 says to use for your own posts and emphasizes permanence, guiding when to invoke. Could be improved by naming specific alternative tools for other operations.

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