cancel_claim

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

With no annotations, the description carries the full burden; it does disclose the operation is a WRITE and that it targets a pending claim. However it never explains the `confirm` flag's role, whether cancellation is reversible, or any permission/rate-limit constraints for a mutating call.

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 lines, front-loaded with the WRITE flag and the core action, followed by prerequisite and usage context. No filler.

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?

An output schema exists so return values need no explanation, and the core action is covered. Gaps remain for an un-annotated mutation: the confirm parameter and any destructive/reversibility semantics are unaddressed.

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% and there are 4 parameters. The description clarifies only `transaction_id` (retrieve it from `pending`) and leaves `leg`, `confirm`, and `league_id_` entirely undocumented — notably `confirm`, which materially changes invocation behavior.

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 ('Withdraw one of your pending waiver claims') with an explicit WRITE marker. It is clearly distinguishable from the sibling `pending` (which it names as the source of the id) and from `waiver_claim`.

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 concrete usage window ('when news lands after a claim goes in and before waivers process') and a prerequisite action ('Get transaction_id from `pending`'). No explicit when-not-to-use or statement of what happens to the claim after cancel, but the context is clear.

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