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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false; the description adds substantial context on top — rate limits, the daily org quota, the required publish scope, and the human-only escalation path for privileged roles. The one gap is that it never says what 'destructive' means here, i.e. whether the previously emailed link is invalidated when a new one is sent.

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?

Front-loads the action and the renewed window, then layers constraints. Dense and largely waste-free, though the trailing parenthetical and the scope sentence read as cramped afterthoughts rather than integrated guidance.

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 one-parameter action tool with no output schema, it covers permissions, role limits, rate limits and environment availability — everything needed to avoid a failed call. It stops short of describing the response shape, which matters since idempotentHint=false makes it useful to know whether a second call is distinguishable.

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?

There is a single parameter and schema coverage is 100%, with the schema itself pointing to 'list_members invitations' as the source. The description adds no further meaning about the identifier, so the 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?

States a specific verb+resource+scope: re-emails a *waiting viewer* invitation with a renewed 7-day window. The role restriction and the 'again' framing distinguish it cleanly from invite_member (new invite) and cancel_invitation (kill it), even though neither sibling is named.

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 explicit when-not conditions: editor/manager invitations cannot be revived by an agent and must be resent by a person in the app, and the tool is unavailable in an unclaimed sandbox. Also states the throttles (once/minute per invitation, 30/day per org) that constrain when a retry will even succeed.

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