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

Annotations already indicate destructiveness, and the description adds an authorization constraint: only posts belonging to the authenticated user are eligible. It clarifies the target state (draft/scheduled) without contradicting the annotation's destructiveHint.

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, front-loaded sentence contains the essential action, scope, and ownership restrition without any filler. This is appropriately concise for a simple one-parameter mutation tool.

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 operation, the description covers the core action and ownership. However, with no output schema and no parameter definition, it leaves the id parameter and responese behavior to inference, which is a real but minor gap in a low-complexity tool.

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 description does not explain the id parameter at all. An agent must infer that id is the post identifier from the tool name and context, but no explicit guidance or format is provided.

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 action and resource: deleting a post. It also narrows scope with 'draft or scheduled' and ownership with 'belongs to the authenticated user,' which clearly differentiates it from sibling tools like create_post, update_post, and schedule_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?

The description implies the tool is for drafts or scheduled posts and for the user's own posts, providing some context. However, it does not explicitly state when not to use it or mention alternatives such as update_post for published posts.

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