cancel_ext_check

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

Annotations already declare the mutation and safety profile: readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false. The description adds no behavioral context beyond the HTTP endpoint—it does not say what happens on cancellation, whether a completed check can be cancelled, or what the body must contain.

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 short but redundant: “Cancel check” appears twice, and the endpoint line is the only extra information. The repetition does not earn its place, and the overall brevity comes at the cost of under-specification rather than efficient clarity.

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?

Given that this is a mutation tool with annotations, a nested request body, and no output schema, the description is too thin. It omits what a check is, the effect of cancellation, prerequisite states, and any indication of return behavior or error conditions.

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 100%, so the schema already documents checkId, body, and x-trace-id. The description only exposes checkId through the endpoint path and adds no meaning beyond that baseline.

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 the action and resource with the endpoint path, but the visible text is essentially the same as the tool name/title repeated twice. It identifies that this cancels a check, yet gives no scope or qualitative detail about what kind of check or what cancellation means.

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?

There is no guidance on when to use this tool versus siblings such as get_ext_check, start_ext_check, or cancel_ext_check_collection. The description only restates the action and does not mention prerequisites, valid states, or alternatives.

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