Delete Post

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

Annotations already mark destructiveHint=true, and the description goes much further: no undo, no trash, comments/reactions/shares are gone, and apply:true plus a plan_id is required regardless of FB_WRITE_MODE. The Reels caveat explicitly warns about unverified behavior and recommends a post-call read. This is exemplary behavioral disclosure beyond the schema and 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?

Three dense sentences with no filler. The core action is front-loaded, followed by the irreversible consequence, then the operational requirement, then the Reels exception. Every clause earns its place and the most critical safety information is prominent.

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 destructive, irreversible tool with 5 parameters and no output schema, the description covers the essential operational context: prerequisites (dry-run plan, confirm token), side effects, the scheduled-post use case, and a verification step for an uncertain Reels path. Nothing that an agent needs to avoid a dangerous call is missing.

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 100%, so the baseline is 3. The description adds cross-parameter operational meaning: apply:true and plan_id must be used together for irreversible writes, the plan must come from a preceding dry run, and the post must have been created by this same app. That goes beyond the isolated schema descriptions.

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 Page post the app itself created'. It also adds a distinguishing behavior — deleting a scheduled post is 'the only way to cancel it' — which separates it from update_post and other siblings. No ambiguity remains about what this tool does.

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 gives clear when-to-use context: app-created Page posts, including scheduled ones. It also says Reels are unverified on this endpoint and advises re-reading the Page afterward. It does not explicitly name sibling alternatives like update_post for editing instead of deleting, but the purpose is unambiguous enough that this is a minor gap.

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