list_members

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

With no annotations, the description carries the burden. It discloses that only active members are returned and includes the output fields (IDs, names, emails, roles, status), which is useful. However, it omits details like pagination, sorting, or case sensitivity, leaving some behavioral gaps.

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 three sentences with no redundancy. It efficiently covers purpose, parameter semantics, and return value, earning every sentence.

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?

This is a simple list tool with one optional parameter and no output schema. The description adequately covers what it does, what the parameter does, and what the response contains. It is complete enough for typical use, though it could mention whether the filter is case-insensitive or partial.

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?

The schema only provides 'query' as a nullable string, providing zero description coverage. The description adds meaning by explaining it is an optional search string that filters by full name, which is essential for correct invocation.

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 the tool lists all active members in the organization, using a specific verb 'List' and the resource 'members'. It distinguishes from sibling tools that operate on pipelines, processes, vendors, etc., eliminating ambiguity.

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?

It provides clear context: lists active members and supports an optional query filter by full name. No explicit when-not or alternatives, but given the unique resource (members) among siblings, this is sufficient for a simple tool.

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