List organization members

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so credit here goes to what the description adds: an auth requirement (owners only), result ordering, and pending invitations only when requested. The id-vs-userId warning is a valuable gotcha beyond anything in the annotations.

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 compact, front-loaded sentences, each earning its place: the resource/ordering/fields, the permission constraint, and the id warning that prevents a real API misuse. No filler.

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?

With no output schema, the description carries the return-shape burden and does so (members with role and state, optionally invitations, oldest first), and it discloses the owners-only prerequisite. Pagination behavior for limit/offset is the only notable omission for a tool of this complexity.

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%, and the description compensates only partly: it explains includeInvitations ("optionally also its pending invitations") and the organizationId context, but is silent on limit and offset. Those are conventional pagination parameters, so the gap is modest rather than critical.

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 (members of an organization) plus ordering (oldest first) and returned fields (role, state). The closing note ties it to update_member by clarifying the id vs userId distinction, so an agent can place it among the member tools without ambiguity.

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?

"Owners only, as in the web app" gives a clear permission/context condition for when this call is valid. It stops short of naming alternatives (e.g. invite_member for adding members), but the listing purpose is unambiguous and no exclusions are needed.

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