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

Annotations already declare readOnlyHint and destructiveHint=false, so the safety profile is covered; the description adds the meaningful extras: the required ReservationReport (Read) role and the hard 7-day window limit. It does not mention pagination or result-size behavior, which keeps it from a 5.

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?

Essentially one front-loaded sentence carrying purpose, constraints, filters and authorization, followed by the endpoint. Dense but no wasted sentences; the single long clause costs it a point on readability.

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?

For a 7-parameter, no-output-schema report, the description covers what is returned (booked vs available per time slot), the time-window limit, the filter dimensions and the auth requirement. Only the exact result shape and pagination/aggregation granularity remain unspecified.

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% and it already documents each filter, including the cross-references to list_courts, list_event_categories and list_reservation_types. The description restates the filter categories and the 7-day span but adds no format or resolution detail beyond the schema, so the baseline 3 applies.

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?

Names the specific report and defines its semantics inline: 'booked vs available time per time slot' for a bounded period. That is materially different from courtreserve_get_court_availability and the other list-based siblings, so an agent can route correctly 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 the operative constraint (period of at most 7 days) and the optional narrowing dimensions (courts, court types, event types, event tags, reservation types), which is clear usage context. It stops short of explicit when-not-to-use guidance or naming an alternative such as get_court_availability.

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