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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered structurally. The description adds only the mild clarification that role changes and invitations are not performed here, which is useful boundary context but not rich behavioral detail such as pagination or result shape.

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 short sentences with the primary purpose front-loaded and no filler. The second sentence is terse to the point of ambiguity, costing a little clarity for its brevity.

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 single-parameter, non-destructive read with full annotation coverage and no output schema, the description states what is returned (members and pending invitations) and where mutations live. It is nearly complete, missing only sibling disambiguation and any hint about result size or ordering.

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 is a single parameter ('company') with 100% schema description coverage, so the schema already documents it fully as a Summer company ID. The description adds nothing about the parameter, which is the expected baseline when the schema does the work.

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 first sentence gives a specific verb ('List') and two concrete resources ('company members', 'pending invitations'), so the agent knows exactly what it returns. However, nothing distinguishes it from close siblings such as summer_teammates_list or summer_account_companies_list, and the second sentence ('Role changes and invitations stay in Summer') is cryptic rather than clarifying.

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 phrase 'Role changes and invitations stay in Summer' implies a boundary — this tool reads the roster while mutations happen elsewhere — but it never names an alternative tool or states an explicit when-to-use condition. Against a large set of teammates/company siblings, the agent is left inferring which listing tool to pick.

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