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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false), so the description is not burdened with the safety profile. What it usefully adds is the 'pending' scope, implying accepted/revoked invites are excluded. It says nothing about pagination, ordering, or return fields, so it adds only modest context beyond the 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?

A single front-loaded sentence with no filler; the resource and the 'pending' qualifier both carry information. There is nothing redundant given the empty schema and the annotations.

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 zero-argument read-only list tool this is nearly adequate, but there is no output schema, and the description never hints at what a returned invite contains (invitee, role, date, status). It also omits ordering/pagination behavior. Those gaps are minor but real.

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?

The tool takes zero parameters, so per the baseline there is no parameter surface for the description to clarify. The 100% schema coverage with an empty properties object is consistent with the description. Nothing about arguments needs explaining.

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 gives a specific verb (List), resource (Organization's invites), and a scoping qualifier (pending). That distinguishes it in practice from org_invite_revoke and org_member_ls, which operate on other aspects of invites/membership. It stops short of explicitly naming any sibling, so it is clear but not maximally differentiated.

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?

There is no when-to-use or when-not-to-use guidance, and no alternative is named. An agent can infer that it is for checking outstanding invitations, but nothing tells it whether to prefer this over org_member_ls or how it relates to org_invite_revoke after acceptance.

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