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

Goes well beyond the annotations by disclosing that a new emailed link is issued, valid for 14 more days, and that the old link is invalidated — the key side effect an agent must know. Annotations already cover safety flags (not read-only, not idempotent, open-world), and the description correctly does not claim idempotence while noting that repeat calls issue new links.

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, front-loaded with the action and immediately followed by the consequence (link invalidation) and the permission constraint. No filler.

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 two-parameter mutation with no output schema and annotations already covering safety flags, the description supplies the essential behavioral facts: expiry window, email delivery, old-link invalidation, and permission scoping. The only real gap is the undocumented required 'id' parameter.

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 coverage is only 50%: 'org' is documented in the schema but 'id' has no description anywhere. The description never mentions that the required parameter is the invite's id or what identifying form it takes, so it fails to compensate for the coverage gap.

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 ('Send a pending invite again') and the word 'again' plus 'pending invite' distinguishes it from the sibling cloud_team_invite without ambiguity. An agent can tell exactly which operation this is.

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 clear precondition — only invites for roles you may grant can be resent — which implies when this applies (an existing, still-pending invite). It does not explicitly name an alternative (e.g. cloud_team_invite for a brand-new invite, or cloud_team_cancel), so routing is left partly to inference.

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