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

Adds meaningful context beyond the annotations: the post is preserved as a draft, the schedule time is cleared, no network call occurs, and the call is gated on confirm=true. The 'does not delete' statement clarifies the destructiveHint=true flag rather than contradicting it, since the destructive part is the schedule clearing, not post removal.

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?

The purpose and eligibility rules are front-loaded, but 'Nothing goes to any network until it is scheduled again' and 'does not call any network' say the same thing twice in consecutive sentences, wasting space in an otherwise short description.

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 mutation with full schema coverage and descriptive annotations, the description covers eligibility, the confirmation gate, and the resulting state. The only omission is what the response looks like (there is no output schema to carry that), which is a minor gap.

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% and both parameters are already documented, including 'Must be true' for confirm. The description only restates the confirm gate ('Refused unless confirm is true') without adding format or sourcing detail beyond what the schema says.

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 and resource ('Moves a scheduled post ... back to Drafts and clears its schedule time') and immediately bounds the scope by excluding deletions and unsent/published posts. The analogy to the calendar's 'Move to draft' action makes the operation unambiguous and distinguishes it from delete_draft and save_draft.

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?

Gives clear preconditions: the post must be scheduled but not yet sent, and confirm must be true or the call is refused. It does not explicitly name sibling alternatives (delete_draft, save_draft, schedule_post) for the adjacent cases, which keeps it short of a 5.

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