delete_post

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

The description labels this as a destructive action ('Delete'), but does not disclose behavioral traits such as irreversibility, required permissions, or what happens if the post is not found. No annotations are provided to supplement this.

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?

The description is a single concise sentence with no superfluous words. However, it may be too brief for a tool with multiple parameters.

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?

Given the lack of output schema and three parameters, the description is incomplete. It does not explain return values, error handling, or prerequisites like needing ownership or authentication, which a delete tool typically requires.

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?

The description does not add any meaning beyond the input schema. While schema coverage is 67%, the param 'post_id' lacks a description, and the optional account/cookies are not explained in context. The schema already provides basic descriptions, so the description adds no 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?

The description clearly states 'Delete a Grok media post' with a specific verb and resource, and it distinguishes itself from sibling tools like like_post, create_media_post, and get_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?

No guidance is provided on when to use this tool versus alternatives, such as when the post is deletable or if there are restrictions. The description lacks context for appropriate usage.

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