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

Because annotations already declare readOnlyHint=true and openWorldHint=false, the safety profile is covered. The description's one addition is that pending invites are included alongside members, which is useful scope context, but it says nothing about response shape, pagination, or whether invites count against seat limits.

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?

One compact fragment with no filler, and the most informative element (roles, pending invites) is up front. It is slightly under-specified rather than bloated, which is a different problem than verbosity.

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 one-optional-parameter read-only list with annotations covering safety and no output schema to explain return values, what is present is adequate. Missing is any statement of scope limits (all members vs a page) and clarification of whether pending invites are merged into the member list or returned separately.

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 100% and the single `org` parameter documents its own default ("your first org"), so the schema explains how to use the parameter. The description adds nothing about org id format or multi-org scoping; by the high-coverage rule, the baseline score of 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?

The phrase "Who's in the org, with roles, and pending invites" names the resource and its contents, so an agent can tell it deals with team membership. But it is a noun fragment with no verb and no differentiation from nearby siblings such as accounts_list or cloud_org_list, which also enumerate org-scoped entities.

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 gives no indication of when to call this instead of alternatives, and there are many plausible alternatives (accounts_list, cloud_invites_get, cloud_org_list, cloud_team_role). It also does not note that this is the read-only counterpart to cloud_team_invite/cloud_team_remove.

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