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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds value beyond them: nonmember read access, deterministic ordering by account ID, the cursor termination rule, and the fact that invite data is member-only and that invite_url is share-safe. That is substantive access and traversal context.

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?

The core purpose and pagination rule are front-loaded, which is good. But the final sentence enumerates every invite return field (id, email, alias, sender, timestamp, invite_url) despite an output schema existing, which is redundant bulk that dilutes the useful access and cursor guidance.

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-value explanation is unnecessary; the description wisely spends its budget on access rules and pagination. What is missing is any treatment of the `limit` parameter and whether invites appear for nonmember readers.

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 coverage is only 33%: only `team` is described in the schema. The description partly compensates for `cursor` by explaining the follow-until-null loop via members.nextCursor, but the `limit` parameter (default 50, max 100) is never explained anywhere, leaving a genuine gap.

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?

Opens with a specific verb+resource: "Read team metadata and members." That distinguishes it from the team-mutation siblings (team_add_member, team_set_member_role), though it never names team_list or workspace_show, which are the nearest ambiguous neighbors, so the agent must infer the split.

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?

"Authenticated discovery permits nonmembers" and "A member also reads invites" give real access-condition guidance about who sees what. However, there is no explicit when-to-use-this-vs-team_list or when-not guidance, so the alternative selection is left implicit.

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