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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful caveat – invitation tokens and acceptance links are never exposed – but the trailing sentence about configurable MCP approval and 'business workflow approvals always apply' is vague boilerplate that doesn't tell the agent anything actionable about this read operation.

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 purpose is front-loaded in the first sentence, which is good. However, the third sentence is lengthy boilerplate that doesn't earn its place in a list operation's description, while the parameters that actually need explanation go unmentioned.

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 detail is rightly omitted, and the annotations plus a simple list operation mean little behavioral context is needed. The remaining gap is the entirely undocumented parameter set at 0% schema coverage, which the description does nothing to close.

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 0% across three parameters (id, limit, offset), so the description carries the full burden and does not meet it. It never explains what 'id' identifies (invitation, team, or organization), nor that limit maxes at 100 and defaults to 50 for paging.

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 pending organization team invitations'), with 'pending' and 'organization' narrowing scope meaningfully. It doesn't explicitly name the adjacent tools (list_organization_users, invite_team_member, resend_team_invitation, revoke_team_invitation), but the pending-status qualifier is enough to distinguish the operation.

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?

Use is implied – reviewing outstanding invitations – but there is no explicit statement of when to choose this over list_organization_users or when a resend/revoke lookup is the better call. No prerequisites or exclusion conditions are given.

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