Delete a post

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

Annotations already flag destructiveHint and idempotentHint, and the description adds what they don't: irreversibility ('Cannot be undone'), a platform-level auth constraint (Facebook Login requirement, attributed to Meta), and a confirmation-gating flow. These are exactly the behavioral facts an agent needs before firing a destructive call.

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?

Three compact sentences, front-loaded with the core action and scope, then eligibility, then safety. No filler or restatement of the title.

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 no output schema, the description covers scope limits, auth eligibility, irreversibility, and the confirmation gate. Only minor gaps remain, such as what the call returns on an already-deleted target despite the idempotent hint.

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 67% and media_id has no description at all; the description compensates by clarifying that the ID may refer to a post, reel, story, or carousel, and that individual carousel children are not valid targets. 'The user confirms first' also implicitly explains when confirmation_token becomes usable, though it doesn't spell out the two-call handshake explicitly.

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?

Names a specific verb ('Permanently delete') and enumerates the exact resources it acts on: post, reel, story, whole carousel. It also carves out a scope boundary ('single carousel items cannot be deleted') that no sibling tool covers, so an agent can distinguish it from delete_comment and delete_template immediately.

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?

Gives a hard eligibility rule ('Only for accounts connected with Facebook Login') that determines whether the tool can be called at all, plus the precondition that the user confirms first. It doesn't point at alternative tools, but there is no competing deletion path among the siblings, so the missing explicit 'use X instead' is minor.

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