list_organization_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 says 'list' which implies a read operation, but it does not mention pagination, ordering, or any potential effects. Given the simple action, more context like 'returns all members with pagination support' would improve transparency.

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, concise sentence that efficiently states the action. It has no unnecessary words, but it is minimal to the point of being under-specified, so it earns a 4 rather than a 5.

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 there is no output schema, the description should clarify return values (e.g., a list of members, pagination info). It does not mention pagination behavior, error conditions, or permission requirements. The presence of sibling tools like search_organization_members is not mentioned, making this incomplete relative to the tool's ecosystem.

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 input schema has 100% coverage for parameter descriptions, so the baseline is 3. The tool description does not add any extra meaning beyond what the schema already provides for page, perPage, and organizationId. It simply echoes the action without elaborating on parameter usage.

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 user members in an organization, using a specific verb and resource. However, it does not differentiate from sibling tools like search_organization_members, which might also list members with filtering, so it's not fully distinguishing.

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?

There is no guidance on when to use this tool versus alternatives. The description merely states the action without context, exclusions, or references to sibling tools like search_organization_members or get_organization_member_info.

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