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

With annotations already declaring readOnly/idempotent/non-destructive, the description goes further: it discloses the authorization requirement (Owner or Admin) and that the result also contains pending invitations, not just active members. It also grounds the tool in a known UI location ('Mirrors Settings › Members').

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?

Front-loaded with the resource and its returned fields, then auth, then downstream routing — a sensible ordering. It is one very dense passage, and the parenthetical project-reach enumeration could be tightened, but no sentence is wasted.

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?

No output schema exists, so the description carries the burden of describing return contents, and it does so in detail (field list, project-reach variants, invitation inclusion) while also covering the auth prerequisite. Nothing needed to call or interpret this tool is missing.

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?

The tool takes zero parameters, so the baseline is 4. The description instead documents the shape of returned identifiers (id vs userId) and their intended consumers, which is useful but strictly outside parameter semantics.

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 ('Everyone in the organization') and enumerates exactly what is returned — member id, userId, name, email, role, joined date, project reach, plus pending invitations. It is also distinguishable from siblings like list_projects or list_access_groups because it names the exact entities it emits.

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?

Gives an explicit prerequisite ('needs Owner or Admin') and concrete downstream routing: 'Use id with set_member_role, remove_member and resend_invitation, and userId with grant_project_access and the access rule and group tools.' That tells the agent both when to call this and which identifier to pass where.

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