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

Annotations already declare destructiveHint=true and openWorldHint=true, so the bar is lower. The description adds valuable specificity by naming what is destroyed: unpublished posts in the connected social scheduler. It still omits irreversibility, permission requirements, and the effect on already-published posts, but the destruction target is a meaningful addition 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 a single front-loaded sentence with no filler or repetition. It states the action and its key side effect efficiently, with every clause earning its place.

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 external mutation with three undocumented required IDs and no output schema, the description covers what happens but not parameter semantics, prerequisites, or alternatives. The annotations cover the safety profile, but the description does not compensate for the complete lack of schema parameter documentation.

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%, and all three required parameters (projectId, siteId, campaignId) lack any schema description. The description adds no meaning, format, or source information for these identifiers, leaving the agent with only parameter names and string types.

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 (cancel) and resource (campaign), plus the concrete effect of removing unpublished posts from the connected social scheduler. This implicitly distinguishes it from pause/resume/activate siblings, but does not explicitly name any alternative, so sibling differentiation is not fully explicit.

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?

The description gives no when-to-use or when-not-to-use guidance. It does not mention pause_distribution_campaign, resume_distribution_campaign, or update_distribution_campaign as alternatives, nor does it state prerequisites or confirmation requirements for cancellation.

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