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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description adds two things the annotations do not: that the operation dispatches email to an external recipient and that it is gated behind an approval step. It does not explain what "rotate" invalidates or that expectedAclVersion is a concurrency guard.

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?

Two short front-loaded sentences with no filler; the action is stated first and the side effect/approval caveat second. Nothing is padded, though it is arguably terse for a destructive external-effect operation.

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?

An output schema exists, so return values need not be explained. However, for a destructive, externally visible, approval-gated mutation, the description omits what rotation invalidates (the prior invitation link), how the approval step surfaces to the caller, and the meaning of the required expectedAclVersion guard.

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 25%: only idempotencyKey is documented (thoroughly) in the schema; sheetId, invitationId and expectedAclVersion have no descriptions anywhere. The description mentions no parameters at all, so it does nothing to compensate for the uncovered concurrency and identity parameters.

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 pair and resource: "Rotate and resend a pending sheet invitation." An agent can distinguish it from sheets_revoke_invitation (which removes access rather than reissuing) without opening a schema. It stops short of explicitly naming the sibling it is not, so it is clear but not fully 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?

"pending" implies the precondition (only a still-pending invitation can be resent), but there is no explicit when-to-use/when-not guidance and no routing to alternatives such as sheets_revoke_invitation or sheets_share_with_email. Usage is only implied.

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