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

With no annotations provided, the description carries the full burden, and it does so well. It discloses side-effect boundaries ('never cancels a submitted task'), the behavior when already claimed ('preserve the original receipt and follow its recovery action'), and a critical caveat about token expiration. These are exactly the non-obvious behavioral traits an agent needs to know.

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 compact and front-loaded with the core action. Every sentence adds value: the action, the claimed-draft behavior, the submitted-task warning, and the required parameter with an example.

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-argument tool with no output schema and no annotations, the description covers action, scope, edge cases, parameter requirement, and an example. Nothing essential for calling the tool 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 0%, so the description must compensate. It explicitly marks confirm_token as REQUIRED and provides a concrete example with a representative value. It implies the token identifies the draft to deny, though it could more explicitly state where the token comes from.

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 ('Deny'), a specific resource ('unclaimed campaign draft minted by campaigns_quick_create'), and a clear scope. It distinguishes itself from related siblings like campaigns_quick_create_confirm and campaigns_quick_create by emphasizing unclaimed drafts and the quick-create origin.

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?

Clearly indicates when to use the tool: to deny an unclaimed campaign draft. It also gives important contextual limitations, such as 'never cancels a submitted task' and the warning about expired/missing tokens. It does not explicitly name alternative sibling tools, but the usage context is unambiguous.

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