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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint, so the safety profile is covered; the description adds genuinely new context: admin/owner-only authorization, no cost, and the fact that mutating invite operations are unavailable through this tool. The status vocabulary (pending, accepted, expired, revoked) also tells the agent what values to expect.

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?

It is compact and front-loads the resource and returned fields before the access and cost notes. The dashboard-mutation sentence earns its place as a scope boundary, though the colon-separated field list reads more like schema echo than prose.

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?

With no output schema, the description usefully enumerates the returned fields and their possible statuses, plus auth requirements. The one gap is that it never states the default behavior, that accepted/expired/revoked invites are excluded unless include_closed is set, which an agent must infer from the schema.

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 parameter include_closed is documented in the schema, so the description need not restate it. The description does not reference include_closed at all, so it adds no meaning beyond the schema; 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?

The description names the resource (invitations to the organization) and enumerates the fields returned (email, role, teams, status, expiry), so an agent knows exactly what this retrieves. It never uses an explicit verb like 'list', relying on the title, but the content is unambiguous and differentiated from list_members by the invite framing.

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?

It states the access restriction ('Admins and owners only'), the cost ('Free'), and the auth options ('API key or a connected account'). It also draws a clear boundary by saying sending/resending/revoking happens on the dashboard, which tells the agent this tool is read-only. It does not point at a sibling tool for related tasks such as checking current membership.

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