Delete Facebook Page Post

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

Annotations already declare destructiveHint=true. The description adds that the action is 'permanent and cannot be undone', reinforcing destructive nature. It also notes authentication via page_id in the Args section. No contradictions.

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-sentence description plus Args list: first sentence states purpose and permanence, second introduces Args. No wasted words, 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?

For a simple delete tool with full annotations and schema, the description adequately covers purpose, permanence, and parameter usage. Could mention consequences like deletion of associated comments, but not essential for basic use.

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 both parameters with descriptions (post_id: get from meta_get_posts, page_id: for token). Description repeats these in Args without adding new meaning. With 100% schema coverage, baseline is 3; description adds minimal extra value.

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?

Description clearly states the tool deletes a Facebook Page post, using specific verb 'Deletes' and resource 'post from a Facebook Page'. It distinguishes itself from sibling delete tools (e.g., meta_delete_ad, meta_delete_comment) by specifying the target is a page post.

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?

While it warns 'this action is permanent and cannot be undone', it does not explicitly compare with alternative deletion methods or specify when not to use it. The context of deleting a page post is clear but lacks explicit when-not guidance.

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