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

Annotations already cover the safety profile (readOnly, non-destructive), and the description adds genuinely non-obvious behavior: that a family member id returns the whole family's reservations, and that the Member (Read) role is required. The underlying endpoint is disclosed too. It does not describe pagination behavior itself, leaving that to the schema.

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 is returned, then the identity rule, then the permission requirement. The field enumeration earns its place; nothing is padded. Slightly telegraphic phrasing ('type, start/end, courts') but efficient.

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 compensates by listing the returned fields, and it covers the identity and permission prerequisites. For a read-only, five-parameter filtered lookup this is close to complete; only the sibling-selection guidance is missing.

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%, so the schema already documents limit, date bounds and the two id parameters in detail. The description only restates the id choice and the default 'upcoming' window, adding marginal meaning beyond the structured fields. 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 the resource precisely (a member's court bookings and event registrations) and even enumerates the returned fields (type, start/end, courts, event name, players). It is clearly member-scoped, which implicitly separates it from courtreserve_list_reservations, but it never names that sibling to make the distinction explicit.

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?

'Upcoming (or dated)' and 'give the member id or your own external id' imply the usage context, and the required Member (Read) role is stated. However, there is no explicit guidance on when to prefer this over courtreserve_list_reservations or courtreserve_list_event_registrations, so the agent must infer the choice.

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