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

Annotations already declare readOnlyHint/idempotentHint, so the safety profile is covered; the description adds the permission gate and the exclusion filter (accepted invites omitted), which is real context an agent can't get from structured fields. It doesn't mention whether results are paginated or how many invites come back, but that is a minor gap given annotations.

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?

Three short sentences, scope first, then the restriction, then the related action. No filler and every sentence carries information.

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, read-only list tool with full schema coverage and annotations, the description covers scope, permission, and the natural next step. The only missing piece is disambiguation from list_team_invitations.

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?

Only one parameter and schema description coverage is 100% ('Team ID from list_teams.'), so the schema carries the meaning. The description adds nothing about teamId itself; baseline 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 plus a scope qualifier ('invitations that were not accepted yet'), which tells the agent this is a filtered read. However it never distinguishes itself from the sibling list_team_invitations, leaving the agent to guess which one returns pending vs. all invites.

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?

Gives a hard prerequisite ('Owners and admins only') and points to the follow-up action ('Revoke one with revoke_invite'), which is a genuine routing hint. It does not explicitly say when to prefer this over list_team_invitations, so it falls short of full alternative routing.

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