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

Annotations only flag destructiveHint=true, idempotentHint=false, and openWorldHint=true; the description goes well beyond them by stating what is actually affected (holds every scheduled post in scope, blocks Post now), that a preview is returned before commitment, that resume requires admin while pause needs only Publisher, and that missed posts stay paused and never publish on their own.

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?

A single dense paragraph, front-loaded with purpose, then constraints, then per-action detail. Every sentence carries operational information, though the unbroken block is long enough that an agent must parse several sentences before reaching the action-specific rules.

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 destructive, non-idempotent, three-mode tool with no output schema, the description supplies the missing return information (preview shows scope and held-post count; resume returns missed post IDs) and the full permission and confirmation workflow, so nothing needed to call it safely is absent.

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%, so the baseline is 3, but the description adds real semantics the schema does not: confirm omitted yields a preview (pause) versus a required post-agreement confirmation (publish_missed) and is unneeded for resume, and post_ids must come from the resume output. Only minor gaps remain, such as the 500-item cap and workspace_id defaulting behavior, which the schema already carries.

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?

Opens with a specific verb pair and resource plus scope: 'Pause or resume publishing for a whole workspace or one brand'. It is immediately distinguishable from list_publishing_pauses (read-only inspection) and pause_subscription (billing), both of which appear in the sibling list.

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?

Explicit when-to-use and when-not: 'check it first with list_publishing_pauses', 'Only act when the user asks; never pause on your own initiative', and a named alternative (list_publishing_pauses) for the inspection step. It also prescribes the exact two-call preview-then-confirm sequence and the permission tier required for each action.

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