list_members

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It describes the operation as a read (list) and details pagination, but does not disclose required permissions, rate limits, or whether the list is scoped to the authenticated user's organization. Key behavioral traits are missing.

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 relatively concise at five lines, with front-loaded purpose. Each sentence (scope, pagination, returned fields) adds value. Minor improvement would be further condensing the pagination explanation.

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?

Given that an output schema exists (covering return structure), the description adequately explains pagination and returned fields. However, it omits context on authorization requirements (e.g., admin only) and whether the list covers all org members or only those visible to the caller.

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 100%, so parameters are already described. The description adds valuable pagination guidance (pass last user_id as 'after_id') and clarifies that 'limit' controls page size. This enriches understanding beyond the basic schema definitions.

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 organization members' with a specific verb and resource. It distinguishes from sibling 'list_workspace_members' by indicating organization-level scope, and enumerates the returned fields (id, email, name, role, timestamps).

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 guidance on when to use this tool versus alternatives such as 'list_workspace_members'. It lacks explicit when-to-use, when-not-to-use, or exclusion criteria, leaving the agent to infer scope from the tool name alone.

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