list_account_members

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'List all members' which implies a read operation, but it does not disclose pagination behavior, potential rate limits, or any other traits beyond the obvious. The description adds no significant behavioral context beyond what the name already suggests.

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, front-loaded sentence that communicates the core purpose without any waste. It is appropriately sized for a simple list operation.

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?

The description plus the input schema and output schema provide enough to invoke the tool correctly: the required account_id is clear, pagination parameters are self-explanatory from the schema, and an output schema exists. However, the description lacks guidance on usage boundaries or any additional behavioral context, making it minimally viable but not thorough.

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 has 0% description coverage for its three parameters. The description clarifies that 'account' refers to an 'organization', adding slight meaning to account_id, but it completely ignores the pagination parameters (page and per_page). It fails to compensate for the schema's lack of descriptions, especially for pagination semantics.

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 action ('List') and the resource ('all members of an account'), and it distinguishes itself from sibling tools like list_accounts (which lists accounts) and list_project_members (which lists project members) by specifying 'account (organization)'.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention that it is the appropriate tool for listing account-level members or that list_project_members should be used for project members, leaving usage context implied at best.

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