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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the description's added value is the ReservationReport (Read) role requirement, the 31-day window cap, and the underlying endpoint. It does not mention pagination behavior or result ordering beyond what the schema says about truncation.

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 what the tool returns before the period constraints, the role, and the endpoint. No sentence is redundant.

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?

With no output schema, the description adequately covers inputs, permissions, and window limits, but it never characterizes the returned rows (shape, ordering, whether cancelled-by/member fields appear). That is a minor gap for a read-only listing tool.

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%, setting a baseline of 3, but the description adds genuine meaning: the 31-day maximum applies per period ('at most 31 days each') and at least one date period must be supplied even though none is schema-required. That materially changes how an agent fills the five optional-looking parameters.

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 a specific verb and resource ('Cancelled court reservations') and clarifies the two filtering dimensions, which distinguishes it from courtreserve_list_reservations. It stops short of naming any sibling explicitly, so an agent must infer the distinction from the 'cancelled' qualifier.

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?

'Give at least one period' supplies a real usage constraint that the schema does not enforce (required params = 0), and the two date-mode framing tells when each filter set applies. There is no explicit statement of when to prefer this over courtreserve_list_reservations or the cancelled event registrations sibling.

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