Instagram post delete

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that: permanent/irreversible deletion, the own-posts-only restriction, and an INSSIST PRO entitlement requirement. It stops short of noting pacing/rate-limit behavior for the non-instant path.

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?

Four short sentences, each load-bearing: action, scope restriction, irreversibility, and the routing to the alternative, with the PRO caveat parenthesized at the end. Nothing is padded.

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 3-parameter destructive tool with annotations covering the safety hints and no output schema, the description supplies the constraints an agent needs before calling. Minor gap: no mention of failure modes or what happens to a scheduled post if attempted here, though the draft_delete pointer mitigates that.

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 description coverage is 100%, so the schema already explains post, instant, and instance. The description adds no parameter-level detail beyond that (e.g., accepted id formats or when instant is appropriate), so the baseline 3 applies.

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 a specific verb and resource ('Permanently delete a published Instagram post') plus the scope qualifier 'published'/'own posts only'. This is enough for an agent to separate it from ig_post_edit, ig_fetch_post, and draft_delete without opening any schema.

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 names the boundary condition ('Own posts only') and a concrete alternative with its selecting condition: drafts and scheduled posts go to draft_delete. It also flags the irreversibility constraint, so the agent knows when not to call it without confirmation.

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