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

Annotations already declare destructive=true and non-idempotent, but the description adds substantive behavior beyond that: atomic batch semantics, that draft schedules revert to drafts, that published content and receipts are preserved when deliveryJobId is supplied, and the explicit no-op on social platforms. This is exactly the kind of outcome disclosure a destructive tool needs.

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?

Five short sentences, front-loaded with the action and scope, then mechanics, then refusals, then the cross-platform disclaimer. Each sentence carries information; density is high but nothing is redundant.

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 single-parameter, no-output-schema mutation tool, the description covers atomicity, allowed batch size, edge-case behavior for drafts, and refusal conditions, leaving little ambiguity. Authorization requirements and any response/error shape are not mentioned, which is the only meaningful 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 description coverage is 0%, so the description must carry the load, and it does for the non-obvious field: deliveryJobId's source (getCalendar) and its effect (preserving published content and receipts), plus the implicit 50-item cap echoed from maxItems. kind and id are left to the schema's enum/uuid typing, which is largely self-evident.

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 opens with a precise verb+resource ('Cancel scheduled publishing') and immediately bounds the scope: up to 50 future schedules, atomic. It also explicitly disclaims a plausible misreading ('does not remove anything from social platforms'), which cleanly separates it from publish/delete style siblings.

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 supplies a concrete routing rule — pass deliveryJobId from getCalendar for separate cross-post deliveries — and enumerates refusal conditions (publisher-claimed content, already-published content, uncertain outcomes), which function as when-not guidance. No sibling tool is named as an alternative, so it falls short of a full 5.

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