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

Annotations already flag destructive and idempotent, but the description adds real substance beyond them: the schedule removal is permanent, the creative itself is left intact, and in-flight/published posts are out of scope. It also discloses an authorization prerequisite (admin must enable publishing over MCP) that no annotation conveys.

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?

Front-loaded with purpose, then irreversibility, scope limit, and prerequisite in short clauses with no filler. The trailing permission sentence is terse to the point of being a fragment, which slightly hurts readability.

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?

An output schema exists so return values need no explanation. Given a two-parameter mutation tool, the description covers permanence, side-effect scope, excluded states, and the authorization gate — everything an agent needs to invoke it safely.

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 description coverage is 100%, so both publicationId and brandId are already documented, including the single-brand omission rule. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

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 (call off/cancel) applied to a specific resource (a scheduled post) plus a scope condition (still scheduled, not yet publishing). This clearly separates it from submit_publication and list_publications 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?

Gives an explicit exclusion (already publishing or published cannot be cancelled here) and a prerequisite path via get_workspace for the admin publishing-over-MCP setting. It does not name the alternative tool to use for the published-post case, so it falls just short of full routing guidance.

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