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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is an irreversible write. The description adds the useful scope constraint that only pending/draft queue items are eligible, but it says nothing about what happens on non-queued posts, whether deletion is permanent, or error behavior.

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 with no filler: verb, resource, and scope constraint in one pass. Nothing is wasted or repeated from structured fields.

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?

The tool is simple (one required string parameter), an output schema exists so return values need no explanation, and annotations cover the destructive profile. Only the permanence/eligibility-failure behavior is left unstated, a minor gap for a tool this narrow.

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?

Only one parameter (post_id) and schema description coverage is 100%, with the schema even pointing to list_scheduled_posts as the source of IDs. The description adds no additional meaning about the identifier, so the baseline of 3 is appropriate.

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?

Names a specific verb (Delete) and resource (post) and narrows the scope to pending or draft posts in the queue, which sharply limits what the agent expects it to succeed on. It does not reference any sibling tool, so an agent gets no explicit cross-tool differentiation beyond the verb itself.

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 'pending or draft' qualifier implicitly tells the agent this is for unpublished, queued items only, which functions as weak when-to-use guidance. There is no explicit exclusion of published posts, no mention of alternatives like update_post or duplicate_post, and no stated prerequisites.

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