delete_post

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the destructive action ('Delete') and the ownership permission requirement, but it does not address reversibility, cascading side effects (deletion of comments, reactions, or insights tied to the post), or failure behavior. Adequate for a simple operation but not rich.

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?

A single efficient sentence with the action and resource front-loaded and zero filler. The HTTP endpoint and permission note each earn their place without redundancy.

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 one-parameter destructive tool with an output schema, the essentials (action, endpoint, permission) are present. But with zero annotations, the lack of side-effect, reversibility, and error-return notes leaves noticeable gaps an agent would need to invoke it confidently.

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 0% and the schema only carries a title 'Post Id'. The description's 'by ID' maps to post_id and the DELETE /{post-id} endpoint clarifies the parameter's role, adding marginal meaning. However, it gives no guidance on where to obtain the ID (e.g., from get_post or get_page_posts) or its format.

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 (Delete) plus resource (a post by ID) and the exact HTTP endpoint DELETE /{post-id}. Clearly distinguishable from siblings like get_post (a read), delete_comment (deletes a comment, not a post), and graph_api_delete (a generic raw deletion).

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?

Adds the ownership-permissions requirement, which gives useful implicit context for when the tool can legally be used. However, it provides no explicit when/when-not guidance and never routes the agent to alternatives such as graph_api_delete for raw deletions or delete_comment for comment-level deletion, leaving sibling selection to inference.

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