cancel_team_inviteCancel a pending team/staff invite (before it's accepted). To remove an accepted member, use demote_staff_to_guest. Requires event_id + invite_id; you must be a host.
| Name | Required | Description | Default |
|---|---|---|---|
| event_id | Yes | ||
| invite_id | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already convey destructiveness; description adds that the invite must be pending and that authorization is host-only, providing useful context beyond annotations.
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 sentences, front-loaded with purpose, efficient and to the point.
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?
Simple tool with clear parameters and no output schema; description covers purpose, usage, authorization, and alternatives; complete for the task.
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 has 0% description coverage, but description only reiterates required parameters without explaining their meaning or format; parameter names are self-explanatory but minimal added 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?
Description clearly states verb 'cancel' and resource 'pending team/staff invite', and distinguishes from removing an accepted member via demote_staff_to_guest.
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?
Specifies when to use (before acceptance), provides explicit alternative (demote_staff_to_guest), and lists requirements (event_id + invite_id, must be host).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.