list_members

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

Describes paging (skip, take), search filter (q), and location filter, implying read-only behavior. No annotations exist, so description carries full burden; fairly transparent but lacks mention of ordering or inactive member handling.

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?

Concise, well-structured with headings and bullet points. Every sentence adds value without redundancy.

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?

Covers main usage and parameters; output schema handles return values. Omits ordering details but acceptable for a list tool. Could mention result limits or behavior for invalid queries.

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?

All four parameters are described with clear purpose and defaults, compensating for 0% schema coverage. Provides context like paging offset, page size, substring matching, and location filtering.

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 club members' with specific verb and resource, and distinguishes from sibling tools like get_member (single) and create_member (mutate) via examples.

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 'Use when:' section with example user intents. Implicitly differentiates from get_member for single lookups, but does not explicitly state when not to use.

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