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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=true) by disclosing that the call only stages a request requiring out-of-band owner approval with a PIN in a browser, and by giving an explicit security instruction never to request or accept the PIN in chat. That is exactly the kind of non-obvious workflow and auth detail annotations cannot convey.

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 tight sentences, front-loaded with the action and scope, followed by the approval-flow caveat and the security rule. Every sentence earns its place with no filler.

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 two-parameter mutation with no output schema, the description covers the crucial missing pieces: that the effect is deferred pending owner approval, and the PIN handling rule. Nothing an agent needs to invoke this correctly is absent.

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 100%, so both parameters (email, workspace) are already documented, including the multi-workspace note and the pointer to list_workspaces. The description adds only that the email is the invited address, which is a restatement, so the baseline 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 (Cancel) and resource (a pending invitation) plus the targeting key (the invited email) and the ownership precondition. This clearly separates it from invite_member (which creates the invitation) and remove_member (which removes an existing member, not a pending invite).

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 clear context for use: only pending invitations, only workspaces you own, addressed by email. It stops short of explicitly naming the adjacent tools (invite_member, remove_member) or stating when this is the wrong choice, so the agent must infer the boundary.

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