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 still adds real behavioral facts: test memberships are silently excluded and the underlying APIv4 Membership.get semantics apply. It omits pagination defaults and result shape, but the schema covers limit/offset.

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?

Two compact sentences with the returned fields first and filters second; no filler. The opening is a noun phrase rather than a sentence, which costs a little immediate clarity.

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 enumerating returned fields, and it flags the hidden test-membership exclusion. Pagination and limits are left entirely to the schema, which is acceptable given 100% schema coverage.

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 each of the seven parameters is already documented with examples and formats. The description restates the filter set (contact, status, type, end-date) but adds no syntax or edge-case meaning, and notably omits ends_after while mentioning only 'ending before a date'.

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 (memberships) and enumerates what each record carries (contact, type, status, join/start/end dates), plus the backing API call (APIv4 Membership.get). It is clearly a read/list tool and distinguishable from civicrm_create_membership, though it never explicitly names a sibling.

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 one concrete use case ('those ending before a date (renewal follow-up)') and a default-scope rule ('Test memberships are left out'), which is genuinely helpful. It does not say when to prefer civicrm_query or other list tools, nor any exclusion conditions.

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