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

With no annotations the description carries the full burden, and it does disclose two real behavioral facts: the invite link stops working and admin permission is required. It does not say whether the invitation can be re-issued, what happens if the id refers to an accepted invitation, or what a failure looks like, so the mutation's edge behavior remains opaque.

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, zero filler, and the highest-value facts (what it does, the effect, the permission gate, the id source) are ordered front to back.

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 mutation with no output schema, the definition covers purpose, effect, permission gate, and argument provenance. The only real gap is error/edge behavior for non-pending or invalid ids, which is minor for a tool this narrow.

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 100% (id is documented as a UUID), so the baseline would be 3. The description adds value beyond the schema by stating the provenance of the id — get_workspace.pendingInvitations — which the schema does not, giving the agent a concrete path to a valid value.

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 ('Cancel a pending invitation') and immediately clarifies the scope word 'pending', which separates it from remove_workspace_member or invite_workspace_member in the sibling list. The parenthetical effect makes the operation unambiguous.

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?

'Admins only' gives a hard precondition, and 'Invitation ids come from get_workspace.pendingInvitations' tells the agent exactly where to obtain the required argument in a large sibling set. It stops short of naming the alternative for removing an already-accepted member, but the pending-only framing covers most of the ambiguity.

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