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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds meaningful state context beyond that: the post and its times are preserved rather than deleted, so the agent knows pausing is reversible and non-destructive of metadata.

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, effect first, alternative second — nothing redundant and no restating of the title verbatim.

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 and no output schema, this is nearly complete: effect, reversibility, and sibling routing are all present. A note on error behavior for non-scheduled posts would close the remaining 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% with a single required post_id, so the schema carries the parameter burden and the baseline is 3. The description adds no format hints (e.g. where post_id comes from or whether it accepts a list) beyond what the schema already states.

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?

Specific verb+resource ("Holds a scheduled post") plus the effect stated in plain terms ("so it doesn't go out"), and it explicitly names resume_post as the counterpart so the agent can separate pausing from resuming without opening either 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?

The second sentence explicitly routes to resume_post as the reverse operation, and "scheduled post" scopes which posts this applies to. What's missing is an exclusion: it doesn't say what happens if the post is already published or in draft, or whether reschedule_post should be used instead when only timing changes.

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