list_members

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

With no annotations, the description carries the burden of behavioral disclosure. It correctly indicates a read-only listing operation and that no active-status filter includes both states, but it does not mention pagination, result limits, or matching semantics such as exact versus partial or case sensitivity. These are plausible hidden behaviors for a list endpoint.

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?

A single front-loaded sentence that states the core action, scope, and filter options with no filler. Every clause earns its place.

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 simple three-optional-filter list tool with an output schema, the description is nearly complete: it names the result scope and available filters. It does not explicitly route to get_member for single-member lookups, but this gap is minor and largely covered by sibling names.

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 0%, so the description must compensate; it does map all three parameters to meaningful filter concepts (name, email, active status) and marks them optional. However, it adds no detail about match behavior or how multiple filters interact, so it only partially compensates for the schema's lack of property descriptions.

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 has a specific verb ('Lists') and resource ('all library members'), with optional filters. This clearly differentiates it from single-record siblings like get_member and from mutation tools like register_member/delete_member.

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 description conveys that this is the tool for broad member queries and optional filtering, but it never explicitly states when to prefer this over get_member or how the filters combine. The usage guidance is thus implied by sibling names rather than stated.

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