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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Confirm a campaign-create draft', which implies a mutation but does not disclose what happens on confirm (e.g., whether it creates the campaign, whether it is destructive, prerequisites, or return values). This is a significant gap for a mutation operation.

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 sentence with no wasted words, making it very concise. However, it is under-specified and lacks necessary detail, so while it is front-loaded and efficient, it does not earn its place as a complete description. It is appropriately short but insufficient.

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 simple mutation tool with no annotations and no output schema, the description is severely incomplete. It does not explain the prepare/confirm workflow, what happens on confirm, or any return information. An agent cannot correctly call this tool based solely on the description.

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?

The description adds no parameter meaning. The schema covers one parameter (customer_id) but not draft_id, and the description does not clarify what draft_id refers to (e.g., the ID from the prepare step). With schema coverage at 50%, the description should compensate but does not.

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 clearly states the verb 'Confirm' and the resource 'campaign-create draft', which distinguishes it from other confirm tools for different resources. However, it does not explicitly explain that this is the final execution step after a prepare action, nor does it differentiate from the prepare sibling within the same campaign resource. It is clear but minimal.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention that it should follow the prepare step, nor does it indicate when not to use it. Given the many confirm/prepare sibling pairs, an agent could easily misuse this tool without additional context.

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