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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description contributes beyond that: the required Member (Read) permission, the explicit exclusion of PIN codes and SSO links from results, and the 30/31-day bound on date-range filters — real behavioral constraints an agent could not infer from structured fields.

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?

Four dense sentences with zero filler: purpose and returned fields first, then filters, then paging, then the security/return exclusions. Every sentence carries information an agent needs.

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 13-parameter read tool with no output schema, the description covers return fields, filtering, pagination and auth adequately. The main omission is guidance on the optional include_* enrichment flags, which affect response shape and payload size.

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%, so the baseline is 3. The description summarizes the filter family (member id, family, exact email, phone, created/updated windows) but adds little syntax the schema does not already carry, and the three include_ratings / include_custom_fields / include_marketing_consent toggles go unmentioned.

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 ('List the club's members') and enumerates the returned fields, so an agent can distinguish it from siblings like courtreserve_list_families or courtreserve_get_member_reservations 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 clear context for invocation: which filters exist, the valid date-window limits, and the paging convention ('pass next_page back as page'). It also names the required Member (Read) role. It stops short of naming alternatives or stating when not to use this tool, so it is a 4 rather than a 5.

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