delete_team_invitation

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

No annotations are provided, so the description carries the full burden. It mentions 'Cancel' implying a destructive action, but doesn't disclose critical behavioral traits such as whether this requires admin permissions, if the action is reversible, what happens if the invitation is already accepted, or any rate limits. The description adds minimal context beyond the basic action.

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?

The description is a single, efficient sentence with zero waste. It front-loads the key action and constraint ('Qiita Team only'), making it easy to parse quickly without unnecessary elaboration.

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?

Given the tool's destructive nature (implied by 'Cancel'), no annotations, and no output schema, the description is incomplete. It lacks details on permissions, error conditions, return values, or confirmation of success/failure. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding how to use it effectively.

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%, with the parameter 'email' clearly documented in the schema. The description adds no additional meaning about the parameter (e.g., format requirements or that it must match an existing invitation). With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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?

The description clearly states the action ('Cancel') and resource ('pending team invitation'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'delete_team_access_token' or 'remove_team_member', which also involve deletion/removal operations in the team context.

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 description provides minimal guidance by specifying 'Qiita Team only', indicating a platform restriction. However, it offers no explicit advice on when to use this tool versus alternatives like 'list_team_invitations' to identify pending invitations first, or what prerequisites are needed (e.g., admin permissions).

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