list_organization_users

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

With no annotations, the description must carry behavioral disclosures. It does reveal the pagination pattern ('After fetching each page, client should ask if it should pull next page') and the environmentId format. However, it omits whether this is a read-only operation, error behaviors, or any side effects. It also includes presentation instructions (tabular format) which are not tool behavior. The provided details are useful but incomplete.

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 concise (five sentences) and front-loads the core action. However, it mixes parameter requirements and response presentation instructions without clear separation, and repeats the need for parameters after already mentioning environmentId. The structure is serviceable but could be more organized and less redundant.

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 paginated list tool with no output schema, the description lacks critical details: it doesn't describe the response shape, how to obtain the next page token, error conditions, or whether the operation is read-only. It instructs the agent to ask for the next page but doesn't explain the underlying mechanism. Given the tool's complexity, the description is incomplete.

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 0%, so the description must compensate. It gives the environmentId format ('env_<number>') and hints at pagination via pageToken but does not explain its format or that it is optional. It misleadingly lists pageToken as 'needed' despite not being required. It also does not describe organizationId semantics beyond its name. The description adds some value but is insufficient and slightly inaccurate.

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 clear verb and resource: 'List all users in the selected organization.' This distinguishes it from other list tools like list_workspace_members by explicitly scoping to organization users. However, it doesn't mention alternative tools or contrast with siblings, so it's not fully differentiated. Still, the core purpose is unambiguous.

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 such as list_workspace_members or list_organizations. The description only provides parameter requirements and pagination instructions, not selection criteria. It also states that pageToken is 'needed' when it is actually optional per the schema, which could mislead the agent about invocation.

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