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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description is not obligated to restate mutability. It does add real context beyond them: the invite must be pending, and the caller must be a workspace owner. It stops short of describing what cancellation does to an outstanding invite link or notification.

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 sentences with no filler, and the action plus its precondition are front-loaded. Nothing could be removed without losing information.

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, non-idempotent-looking-but-declared-idempotent mutation with no output schema, the description covers the key constraints: pending state and owner-level authorization. It is slightly thin on failure behavior (e.g., invite already accepted or nonexistent) but sufficient to invoke correctly.

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 required parameter with 100% schema description coverage and a declared pattern, so the schema carries the semantics. The description adds nothing about invite_id format or sourcing, which is acceptable given the coverage baseline.

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 ('Cancel') and resource ('pending workspace invite'), which is precise enough for an agent to distinguish it from invite_member and remove_member. It does not name those siblings explicitly, so differentiation requires inference.

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?

The 'pending' qualifier implies when it applies (unaccepted invites) and 'Workspace owners only' gives a precondition, but there is no explicit guidance on when to use this versus remove_member or how to handle an invite that was already accepted.

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