members_list

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

No annotations are provided, so the description carries the full disclosure burden. The tool is a read operation (listing members), which is clear from the verb. The description discloses the access restriction (admins/owners only) and indicates what fields are returned. Since this is a read-only listing tool, the behavioral surface is minimal and well-covered, though it doesn't explicitly mention response format or ordering.

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 sentences, zero filler. The first sentence states exactly what is returned, the second adds the single most important constraint (who can call it). Every word 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?

For a zero-parameter read-only list tool with clear purpose and access requirements, the description is complete. It could theoretically mention pagination or filtering, but with no parameters available, the description covers the essential information an agent needs: what it returns and who can invoke it. A minor enhancement would be noting any pagination behavior.

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 has 0 parameters, so there are no parameter semantics to clarify. The schema is trivial (empty properties object) with 100% coverage by default since there are no parameters. A baseline of 4 is appropriate for a zero-parameter tool where no compensation is needed.

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 clearly states the verb ('List'), resource ('all members of the organization'), and the specific data returned (roles, active status, allowed company access). It distinguishes well from sibling member tools like members_update/members_delete which mutate, and members_permissions_reference which references permissions. The 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?

The description states a permission prerequisite ('Only organization admins and owners can list members'), which gives clear context about who can invoke it. However, it does not explicitly discuss when one would choose this over interactions list/invitations_list, nor provide explicit exclusions or alternative recommendations. The access control note is useful context but not a full usage guideline.

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