list_members

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

Annotations already declare readOnlyHint=true, and the description adds useful behavioral context: results are filtered by the caller's permissions and include user details, roles, and MFA status. It does not discuss pagination behavior, but page and size parameters are already documented in the schema.

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: the primary action and resource come first, the parenthetical clarifies terminology, and the return contents are stated compactly. Every clause earns its place with no 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?

For a read-only list operation with fully documented parameters and a readOnlyHint annotation, the description is complete enough. It states the resource type, permission scoping, and return contents; the optional filters and pagination defaults are already captured in the schema.

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 100%: all six optional parameters (id, page, size, status, username, subAccountId) are self-documented in the input schema. The description does not add parameter-level meaning, so it meets but does not exceed the baseline.

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 opens with a specific verb and resource: 'List all Sub-Account members' and clarifies these are Wasabi Console users. This differentiates it from sibling tools like get_member (single member) and list_sub_accounts (sub-account-level resource), and the 'within your permissions' qualifier defines the scope.

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 intended use is implied: use this tool when you need to enumerate Sub-Account members visible to the caller. However, the description does not explicitly mention when to prefer this over get_member for a single member or list_sub_accounts for account-level listing, nor does it state any exclusions.

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