cancel_company_blueprint_certification

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

The description mentions 'unfinalized' which implies a state requirement, but it doesn't disclose what happens to the candidate after cancellation (e.g., deletion, status change, or reversibility). The destructiveHint annotation already flags destructiveness, so the description adds little beyond that.

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, concise sentence with no redundancy or unnecessary detail. It is appropriately brief for the operation it describes.

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?

The description provides minimal context. It doesn't explain what a Blueprint certification is, what a candidate represents, or what the parameters mean. It also doesn't describe the output or error conditions, so an agent lacks sufficient context to use it confidently.

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 schema lists three required parameters (company_ref, project_ref, candidate_id) with no descriptions. The tool description does not mention any of them or explain their roles, leaving the agent without guidance on how to populate them.

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 action (cancel) and the target (unfinalized Blueprint certification candidate), distinguishing it from related actions like finalize or propose. However, it doesn't reference the specific workflow or sibling tools, so it's slightly less than 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 offers no guidance on when to use this operation versus alternatives such as finalize or propose. The word 'unfinalized' hints at a condition, but it doesn't explicitly state the prerequisite or any consequences.

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