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

Annotations already declare destructiveHint/idempotentHint, yet the description still adds real consequence detail: the person's link stops working and all held data is deleted. It also discloses a billing nuance ('one never started does not count against the month') and mandates human confirmation, none of which appears in the annotations.

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?

Three short sentences, front-loaded with the action and its scope, and every sentence carries distinct information. The billing sentence ('One never started does not count against the month') is elliptical enough to be misread on a first pass, which slightly dents an otherwise very tight description.

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?

No output schema exists, and for a destructive single-parameter mutation the description covers the precondition, the exact effect on the subject and their data, a cost side effect, and the required human confirmation. There is no material gap an agent would need filled before calling it.

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?

Only one parameter and schema coverage is 100%, with the schema itself documenting provenance ('from create_id_check or list_id_checks'). The description adds nothing about the id, so this sits at the baseline where the schema does all the work.

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 and resource ('Cancel an ID check') plus a precondition that narrows the target set ('that has not ended'). That precondition alone separates it from get_id_check/remind_id_check in the sibling list, so an agent can pick it without opening the schema.

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?

Gives a clear use condition ('has not ended') and an explicit procedural guardrail ('Confirm with the human first'), which is the right guidance for a destructive action. It stops short of naming an alternative for the already-ended case, leaving the agent to infer that ended checks are not cancellable.

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