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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the agent knows this is an in-world destructive write. The description adds only the draft-only scope; it does not mention irreversibility, whether a deleted draft can be recovered, what happens if the ID refers to a published or scheduled post, or what error behavior to expect. With annotations carrying the safety profile, this partial addition merits a 3.

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?

One short sentence with zero waste, front-loaded with the verb and resource. It is efficient, though the extreme brevity means there is no room for the scoping or recovery caveats a destructive tool would benefit from.

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 tool with full schema coverage and existing annotations, the description covers the essentials. Still missing for a destructive operation are persistence/reversibility behavior and what happens when the target is not a draft, which an agent would need before calling 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?

There is a single required parameter with 100% schema description coverage ('Post ID to delete'), so the schema already fully documents it. The description adds nothing about ID format, whether IDs come from list_drafts or get_post, or how to obtain a valid ID, so the baseline 3 applies.

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 draft post') and the lookup key ('by ID'), so an agent can distinguish it from delete_idea or cancel_post. It does not explicitly name which sibling to use instead for non-draft posts, keeping it below a 5.

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 word 'draft' implicitly scopes usage to draft posts only, which is useful guidance. However, there is no explicit statement of when to use delete_post versus cancel_post, remove from queue, or delete_idea, and no prerequisites or exclusions are given.

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