list_organization_members

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. 'List' implies a read-only operation, which is helpful, but the description does not disclose pagination semantics, potential authorization requirements, or how 'team members and staff' are distinguished. Critical behavioral context like continuation handling is absent.

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 with no filler or redundant qualifiers. It conveys the core action and resource efficiently. It could arguably do more in the same space, but as written it is appropriately concise.

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?

While this is a simple two-parameter tool, the description omits essential context about the continuation parameter and pagination. Given no annotations and a schema with bare parameter names, the description should clarify how listing works across pageston and what 'team members and staff' means operationally. The presence of an output schema reduces the need to describe return values, but usage guidance is still lacking.

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 0%, so the description must compensate for the schema's silence. While 'organization_id' is implicitly referenced via 'associated with an organization', the 'continuation' parameter is entirely unexplained. The description adds no meaning about required versus optional parameters or their formats beyond what the parameter names already suggest.

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 states a specific verb ('List') and resource ('team members and staff associated with an organization'). It clearly distinguishes this from sibling tools like list_organization_roles or list_user_organizations by focusing on members/staff rather than roles or user accounts. However, it does not explicitly differentiate itself from similar 'list' tools.

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?

No usage context is provided. The description does not specify when to use this tool versus alternatives, nor does it mention pagination behavior via the continuation parameter. There is no guidance on prerequisites, exclusions, or when this tool would be a poor choice.

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