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

Annotations already establish that this is a safe, read-only, idempotent, closed-world operation. The description adds useful context that pending invitations are included and defines role/scope/owner semantics, but it omits behavior such as ordering, pagination, or what member fields are returned.

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 description is compact and avoids filler, but it opens with a noun phrase instead of a clear action statement and reads as a fragment. The role and scope definitions are useful but could be structured more clearly for fast scanning.

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?

With no output schema and no input parameters, the description carries some burden for explaining return content. It covers role, scope, owner, and pending invitations, but does not describe the shape of member records or invitation details, leaving meaningful gaps.

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?

There are zero input parameters, so the baseline is 4. The description's role/scope/owner text describes return-value semantics rather than input parameters, which is appropriate given the empty schema.

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 names the resource—people on the team and pending invitations—but never uses an explicit action verb such as 'list' or 'return'. It is understandable from the title and content, but it does not sharply distinguish itself from siblings like invite_member or whoami.

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 provides no when-to-use guidance, no alternatives, and no exclusions. The role and scope text explains return-field meanings, not when an agent should call this tool instead of another sibling.

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