deleteSingleImagePost

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

The description reveals destructive behavior beyond annotations: it cannot be undone via API, removes the post_token, and breaks external links. Annotations already indicate destructiveHint=true, but the description adds specific, actionable side effects. No contradictions with 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 well-structured with headers and sections, but it is slightly verbose. Each sentence serves a purpose, but some phrases (e.g., repeated warnings about destructiveness) could be condensed. Overall, it is efficient and front-loaded with key 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?

The description fully covers the tool's operation: it explains the return value (status and message), side effects (link breakage), and how it differs from alternatives. For a single-parameter delete tool with no output schema, it provides all necessary context for safe invocation.

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?

With only one parameter (post_id) and 0% schema description coverage, the description merely restates that post_id is required. It does not explain the parameter's format, range, or examples of valid values, which would add value. However, given the simplicity of the parameter, the description is minimally adequate.

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 action ('Delete a post - Permanently delete'), identifies the resource by ID, and distinguishes it from the sibling tool updateSingleImagePost for hiding posts. The verb and resource are specific and unambiguous.

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 explicitly states when to use this tool ('Use when: removing a post permanently') and when not to use it (for hiding, use updateSingleImagePost with post_status=0). It also recommends confirming intent with the user before bulk use, providing clear guidance.

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