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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The second sentence hints that mutation of roles/invitations is out of scope, but it is ambiguous ('stay in Summer') and adds little concrete behavioral context such as pagination, ordering, or how pending invites are represented.

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 wasted words. The trailing sentence is slightly cryptic, which keeps it from a 5, but the structure is efficient.

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 list tool with full annotation coverage and no output schema, the description covers the essential scope. It could say a bit more about what the returned member/invitation records contain, but nothing critical to correct invocation is missing.

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% and the single 'company' UUID parameter is fully documented in the schema. The description adds no format, constraint, or semantics beyond that, so the baseline 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?

States a specific verb and resource: 'List company members and pending invitations.' The scope (members + pending invites) is more precise than the sibling 'summer_account_companies_list', but the description never names a sibling or explicitly distinguishes the two, so it falls short of a 5.

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?

'Role changes and invitations stay in Summer' implies a boundary (this tool reads; mutations happen elsewhere), which is weak when-to-use guidance. No alternative tool is named and no prerequisites (e.g., required permissions or company context) are given, so usage is only implied.

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