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

Annotations only flag readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description adds real context beyond that: access is revoked immediately ('They lose access at once'), the confirm-per-call default can be switched off, and the tool requires a Cotlet API key scoped to this app. Missing only finer detail like irreversibility or re-invite behavior.

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?

Front-loads the action and its effect, then operational constraints. Slight redundancy: 'By default you confirm each call' and 'confirm with the user before each call' restate the same idea, but overall it is tight and front-loaded.

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 mutation with no output schema, the description covers the effect (immediate access loss), the confirmation default and its toggle, the cross-user impact, and the auth requirement. That is close to complete; only re-invite/reversibility and error behavior are unaddressed.

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, presentation_id) are already documented with their source hints. The description adds no parameter-level meaning, so the baseline of 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 and resource ('Revoke a collaborator's access to a presentation') and scopes it ('Removes one person from the deck'), which is clearly distinguishable from the sibling invite_collaborator and list_collaborators. An agent knows exactly what this does without opening the schema.

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 strong operational guidance (confirm each call by default, must confirm with the user because it reaches other people), which implies when caution is needed. But it never names an alternative or states when to reach for this removal versus, say, invite_collaborator or list_collaborators to verify the target first. Usage is implied rather than explicitly framed.

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