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

Annotations already cover the non-destructive safety profile, and the description adds meaningful behavior: scheduled and queued posts remain on the calendar, nothing is deleted or moved, resume_queue restores publishing, and the reply reports how many scheduled posts are waiting. This is substantial context beyond the annotations.

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 description is compact and front-loaded with the account-wide scope, followed by behavior, undo path, response detail, and alternatives. Every sentence adds useful information without repetition.

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 no-parameter action tool with no output schema, the description is complete enough to call correctly. It explains scope, side effects, undo, return information, and the relevant alternative, leaving no significant operational 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?

There are zero parameters, so the baseline is 4. The schema is empty and fully covered, and there are no argument semantics to clarify.

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 states a specific verb and resource ('Pause publishing') plus explicit scope ('whole account, every workspace included'). It clearly distinguishes this account-wide pause from per-post alternatives like cancel_post.

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?

It gives explicit when-to-use guidance ('only when the user asks to stop everything'), names the undo path with resume_queue, and routes single-post holds to cancel_post. The alternatives are directly named and the selection condition is clear.

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