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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real value beyond that: it discloses the required permission scope (TEAMS_READ) and the exact set of returned attributes, which matters since there is no output schema. It omits pagination or ordering behavior, keeping it short of a 5.

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?

A single front-loaded sentence plus a GraphQL path and a permission note; every clause carries information and nothing is wasted. Slightly dense but well-structured.

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 read-only two-parameter list tool with full schema coverage and a safety annotation, the definition covers permission requirements and return shape. The absence of an output schema is compensated by the enumerated fields; only missing piece is pagination/ordering context.

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%, so both parameters (teamId, sortBy) are already documented in the schema. The description echoes teamId via the GraphQL path but adds no syntax or format detail (e.g. valid sortBy values) beyond what the schema provides. Baseline 3 applies.

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 ('List') and resource ('members of a team') and enumerates the returned fields (isLead, isOrgAdmin, preferredName, email), so the agent knows exactly what is produced. It does not explicitly differentiate from the similarly named sibling list_organization_users, but the team-scoped resource is clear enough to distinguish them.

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?

Usage is implied by 'List the members of a team' and a prerequisite ('Requires TEAMS_READ') is given, but there is no explicit when-to-use versus alternatives such as get_team or list_organization_users. The agent must infer the routing from the resource name alone.

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