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

Annotations already declare destructiveHint=true, non-readonly and non-idempotent, so the safety profile is covered. The description adds only the "pending" state constraint; it says nothing about the optimistic-concurrency requirement (expectedAclVersion) or what happens on version conflict, which is real behavioral context for this mutation.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though its terseness is arguably part of the specification gap rather than a virtue.

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, but for a destructive, non-idempotent mutation with four required parameters and a concurrency token, the description omits conflict handling, retry semantics, and authorization requirements. Combined with the 25% schema coverage, the tool is under-specified.

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 only 25% — idempotencyKey is documented, but sheetId, invitationId, and especially expectedAclVersion are bare. The description adds no parameter-level meaning at all, so it fails to compensate for the documented 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?

Specific verb plus resource ("Revoke a pending sheet invitation") with a state qualifier that narrows the scope. It does not explicitly distinguish itself from close siblings like sheets_remove_user_access or sheets_resend_invitation, so an agent must infer the boundary.

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?

No when-to-use guidance, no prerequisites, and no named alternative. In a family containing sheets_remove_user_access, sheets_resend_invitation, and sheets_transfer_ownership, the description never says which situation this tool is for.

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