list_memberships

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

No annotations are provided, so the description must cover behavioral traits. It mentions filtering but does not disclose pagination behavior (skip/take), default ordering, or whether it returns all statuses or only active ones. The description is adequate but lacks important details for a listing tool.

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?

The description is a single sentence plus three examples, with no redundant information. Every part serves a purpose, making it concise and well-structured.

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?

Given the output schema exists, return value details are not needed. However, the description lacks clarity on whether it lists all memberships or only active ones (as implied by the example 'what memberships are active?'), and does not explain pagination. This leaves gaps in understanding the full behavior.

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 0%, so the description must compensate. It explains member_id and location_id filters but omits skip and take parameters entirely, leaving pagination semantics unexplained. This is a significant gap for a tool with 4 parameters.

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?

The description clearly states 'List memberships' and specifies optional filters by member or location, distinguishing it from sibling tools like get_membership, create_membership, and cancel_membership.

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?

Provides explicit example queries ('what memberships are active?', 'show member 12345's membership history', 'list all memberships at location 1'), giving clear usage context. However, it does not mention when not to use it or alternatives like get_membership for a single record.

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