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

Goes well beyond the annotations, which only flag destructiveHint=true and non-idempotence. The description discloses concrete side effects: reserved seats are released and paid tickets are refunded in full to the user's wallet at that school. It also adds the permission condition and an explicit confirmation instruction.

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 tight sentences, front-loaded with the action and parenthetical sourcing, then consequences, then permissions, then the safety warning. Every sentence carries distinct, useful information with no padding.

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 not be described. The description covers preconditions (cancellable ticket, ownership), side effects (seat release, refund destination), and the destructive-action confirmation — everything an agent needs to invoke it safely.

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 100% and the schema already documents ticket_id's origin and cancellability constraint. The description repeats the source (list_my_event_registrations) but adds no syntax or format detail beyond it, so baseline 3 is appropriate.

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 (Cancels) and resource (the user's own event ticket), scoping to ownership explicitly. An agent can distinguish it from cancel_my_lunch_order, cancel_my_volunteer_signup, and cancel_program_registration without opening any 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?

Names the source of the required ticket_id (list_my_event_registrations) and states the precondition that only the ticket owner or a coordinator can cancel. It stops short of explicitly naming alternative sibling tools, but the usage context is clear.

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