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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful context beyond them: it clarifies that an already-claimed draft should be preserved, that submitted tasks are never cancelled, and that an expired/missing token does not prove no submission occurred.

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 purpose and caveats are front-loaded in the first sentence, and the REQUIRED/EXAMPLE block aids invocation. Slightly padded by restating a schema-level requirement, but overall tight and well-ordered.

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, no-output-schema tool the description handles the behavioral nuances well and does not need to explain return values. However, it leaves the connection_context parameter undocumented, so it is not fully complete for invocation.

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 0% for both parameters. The description restates that confirm_token is required (already in the schema) and gives a sample value, but the second parameter, connection_context, is entirely undocumented in both schema and description, leaving a real gap.

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 (deny) and resource (an unclaimed campaign draft minted by campaigns_quick_create), scoping it to the 'unclaimed' case and distinguishing it from the confirm flow. It is clear enough to tell apart from the sibling confirm tool, though it never names that sibling explicitly.

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 a clear when-to-use ('deny an unclaimed draft') and an implicit when-not ('if already claimed, preserve the original receipt and follow its recovery action'), plus a boundary condition ('this never cancels a submitted task'). It stops short of explicitly naming the alternative tool to use instead.

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