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

Annotations declare the safety profile (idempotent, non-destructive, write), and the description adds substantial behavior beyond them: queued Pins publish unchanged, arrived-during-pause Pins are not retried, and the publishing_paused/max_pin_limit failure-reason semantics are explained with a date caveat. That is exactly the context annotations cannot carry.

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 trigger condition is front-loaded before the failure-handling detail, and each sentence carries operational information. It is dense and the October 15, 2026 caveat is long-winded, but it describes a real trap rather than padding.

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?

With an output schema present and rich annotations, the description covers the remaining gaps an agent needs: the post-resume state of queued Pins, the non-retry behavior, and the misleading failure reason. Nothing required to call it correctly is missing.

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 accountId parameter is fully documented in the schema, so the baseline is 3. The description adds scope meaning ('whole account') and disambiguation guidance for choosing the account, which is a genuine step above the schema.

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 ('resumes publishing for the whole account') and explicitly positions itself against the sibling pause_publishing. An agent can distinguish it from pause_publishing and the post-level alternatives without opening any 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?

It gives the trigger condition ('after pause_publishing'), the no-op case ('resuming an account that is not paused changes nothing'), and routes failures to list_posts and schedule_post by name. It also handles the multi-account ambiguity by instructing the agent to ask the user rather than choose.

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