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

Annotations only say non-read-only, non-idempotent, destructive and open-world; the description adds real behavioral facts the agent could not infer: per-address hourly throttling, refusal when an invitation is already queued, no seat changes, and an auth/plan gate limited to owner API keys, connected apps and team-seat plans. This exceeds the annotation baseline rather than restating it.

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 delivery-failure condition is front-loaded and every clause carries information (trigger, refusal, rate limit, scope, auth). The telegraphic fragments like "No seat changes." are terse to the point of ambiguity but consume minimal space for the content delivered.

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 an output schema, full annotation coverage and a single well-documented parameter, the description supplies most of what an agent needs for a mutating resend. It still does not say what happens to the prior invitation or its token when a resend occurs, which matters given destructiveHint=true.

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 member_id parameter already documents both its meaning (the teammate's seat id) and its source (list_team_members). The description adds nothing about the parameter, so the standard 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?

"Send a pending team invitation again when its delivery was not confirmed" gives a specific verb, a specific resource, and a narrowing condition. The words "pending" and "again" separate it from invite_team_member without requiring the agent to open either schema.

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?

The trigger condition (delivery was not confirmed) is explicit, and the exclusion (an invitation already queued is refused) tells the agent when this call will fail. It never names invite_team_member as the alternative to use for new invitations, which is the one missing piece of routing guidance.

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