list_organization_users

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

Annotations already declare readOnly=true, idempotent=true, destructive=false and a closed world, so the safety profile is covered. The description adds meaningfully beyond that by disclosing the auth requirement ('Requires the caller OAuth token') and the paginated nature of the result — both non-obvious operational facts.

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?

Three short, front-loaded sentences: scope first, then sibling routing, then the auth prerequisite. No filler and no repetition.

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 simple paginated read with full annotation coverage and a complete schema, the description covers purpose, routing and the OAuth prerequisite. Return shape isn't described (no output schema, but the pagination hint and pageToken param convey continuation behavior), so the remaining gap is minor.

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%, and the schema already documents pageToken, environmentId and organizationId with formats and defaults. The description's only added nuance is the page-at-a-time framing, which is largely redundant with the pageToken description. Baseline 3 is appropriate.

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?

States a specific verb and resource ('List users in one organization') plus the pagination scope ('one page at a time'). It then names the adjacent siblings (get_organization_details, create_organization_user), so an agent can place it precisely within the organization/user tool family.

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?

It routes the agent to the right siblings by stating what each is for ('use get_organization_details to read the organization record', 'use create_organization_user to add a user'), which implicitly distinguishes enumeration from read/write of a single org or user. It stops short of an explicit selection condition or a 'do not use this for X' exclusion, so it is strong context rather than a full decision rule.

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