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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. The description adds genuinely useful scope information beyond that: the deletion is limited to unpublished drafts/scheduled posts and is not a network-level takedown. It omits whether the deletion is permanent or recoverable, which is the remaining behavioral question for a destructive tool.

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 short sentences with zero padding: the action and its scope come first, the boundary condition second. Every clause carries information an agent needs.

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 two-parameter destructive tool with rich annotations and no output schema, the description covers the crucial ambiguity (draft/scheduled vs. published) that could otherwise cause a wrong call. Minor gaps remain around irreversibility and the bulk-delete confirmation requirement.

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 coverage is 100%, so both post_id and many_deletes_confirmed are documented in the schema itself, and the description adds no further meaning for either. The multi-delete confirmation gate — the riskiest parameter here — is left entirely to the schema's terse reference to 'many_deletes', which the description could have clarified.

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 (deletes) and resource (a post), and narrows scope to drafts or scheduled posts before publishing. The second sentence explicitly contrasts with published content, so an agent can distinguish this from publish_post_now, pause_post, or reschedule_post without opening any schema.

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?

Clearly implies when to use it — a draft or a not-yet-published scheduled post — and rules out published posts via the negative clause. It stops short of naming what an agent should do instead for a published post, and says nothing about the bulk-delete confirmation flow implied by many_deletes_confirmed.

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