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

Adds context the annotations cannot convey: annotations flag destructiveHint=true and idempotentHint=false, and the description clarifies that only the schedule is destroyed while content survives as a draft, and that a second call on an unscheduled post errors. It stops short of describing permissions needed or the response payload.

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?

Three short sentences, front-loaded with the outcome, then the mechanism, then the re-schedule path and the error case. Minor redundancy: 'stays as a draft' is stated twice.

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 mutation with full annotation coverage, the description covers outcome, side effects (nothing published or emailed), recovery path, and failure mode. The only gap is that with no output schema, the return value on success is not described.

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 the single parameter is documented in the schema ('Post ID from list_posts'), so the description carries no additional parameter burden. Baseline 3 applies since nothing extra is added or needed.

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+resource ('Stop a scheduled post') and immediately defines the resulting state ('it stays as a draft'), which cleanly separates it from delete_post and unpublish_post in the sibling list. An agent can tell what this does without opening the 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?

Gives clear usage context and names the counter-operation ('Schedule it again with schedule_post'), plus the precondition that a post with no schedule errors. It does not explicitly contrast with delete_post or unpublish_post for the case where the user wants the post gone entirely, which is the main remaining ambiguity.

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