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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuine context beyond that: the required 'Membership Report role (Read)' permission, the fact that results are paged, and the backing endpoint GET /api/v1/membershipreport/list.

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 with zero filler: grain and returned fields first, then filters, then pagination and the auth requirement. Front-loaded so an agent grasps the tool in the first clause.

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 12-parameter, all-optional read tool with no output schema, the description covers what a row represents, that output is paged, and the permission needed. It stops short of describing the response envelope (next_page, totals) but the schema's page description points at next_page, so nothing critical 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 every parameter (including page, page_size, the date ranges and assignment_type) is already documented at the field level. The description only restates the filter families in prose without adding syntax, date format, or interaction rules; baseline 3 is warranted when the schema does the heavy lifting.

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 artifact (membership report) with its exact grain — one row per member or family membership — and enumerates the columns returned (status, billing cadence, start/end, next payment, cancellation history). This lets an agent distinguish it from a plain member listing, though it never explicitly contrasts itself with siblings like courtreserve_list_members or courtreserve_list_membership_types.

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?

The filter dimensions (type, assignment, start/end/next-payment/cancellation dates) imply when the tool is the right choice — when you need report-level data rather than a roster — but there is no explicit when-to-use/when-not or named alternative. The role requirement hints at an access precondition but not at tool selection.

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