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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered structurally. The description adds real value beyond that by stating the operation is permanent and enumerating the post states in which the call is invalid, which is exactly the missing precondition context. It does not describe failure behavior or any recovery path when the constraint is violated.

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 tight sentences with zero filler; the core action and its eligibility constraint are both front-loaded and easy to parse.

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?

An output schema exists, so return values need no explanation, and the annotations carry safety semantics. Combined with the description's permanence and state-restriction statements, an agent has everything needed to decide and call correctly.

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 0% and the single parameter post_id has no description in the schema. The description never mentions post_id, so it adds no format, source, or lookup guidance, though the parameter is largely self-explanatory and implied by the eligibility rules.

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 gives a specific verb ('Permanently deletes') and a well-scoped resource ('a draft or scheduled post'), which immediately separates it from publish_post, schedule_post, and update_post. It stops short of naming a sibling outright, but the eligibility constraint supplies the differentiation.

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 negative constraint ('Published posts, partially published posts and posts currently publishing cannot be deleted') effectively tells the agent the only valid state for calling this tool. It provides clear when-to-use context and exclusions, though it never names an alternative tool for the excluded cases (e.g., update_post or unpublish flows).

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