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

Annotations already establish readOnly/idempotent/non-destructive, so the description's added value is the permissions requirement ("Owners only"), the ordering guarantee, and the important warning that the returned "id" rather than "userId" is what update_member consumes. That last point is a genuine behavioral gotcha not derivable from annotations or schema.

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?

Two dense sentences with no filler: the first covers scope, ordering, fields and the optional flag; the second covers the permission gate and the id-vs-userId caveat. Information is front-loaded and every clause earns its place.

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?

An output schema exists, so return values need not be spelled out, yet the description still usefully characterizes them (ordering, role, state). With annotations handling the safety profile and the description covering permissions and the id caveat, the main remaining gap is pagination semantics for limit/offset.

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 carry the param burden, yet it only covers includeInvitations ("optionally also its pending invitations") and implies organizationId. The limit and offset pagination parameters are never explained in prose, leaving half the inputs undocumented beyond raw schema constraints.

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?

It names the resource (organization members) and specifies the shape of the result: ordering (oldest first), fields (role, state), and the optional inclusion of pending invitations. It also links to update_member, so an agent can place it among siblings, though it doesn't contrast with the other list_* tools explicitly.

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 real eligibility precondition, and the update_member reference implies a follow-up workflow. However, there is no when-to-use/when-not guidance or named alternative for listing members versus other membership-related tools like invite_member or cancel_invitation.

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