beel_delete_invitation

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

Annotations already indicate destructive and idempotent behavior, but the description adds valuable context beyond that: the 404 response deliberately does not disclose which resolved state the invitation is in, and revoking does not remove the invitation from the list. This helps an agent anticipate unusual API behavior without contradicting 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?

The purpose is front-loaded in the first sentence, followed by compact bullet points covering edge cases and side effects. The endpoint is included without redundancy, and every sentence carries distinct operational 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 two-parameter destructive action, the description covers success effects, failure semantics for resolved states, and the persistence of history. It omits the success status code or response body, which is a minor gap given there is no output schema, but overall the definition is nearly complete.

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?

The schema thoroughly describes account_id but leaves invitation_id undocumented, resulting in 50% coverage. The description's endpoint line only restates the path variables and adds no meaningful detail about invitation_id beyond what the schema already implies, so it makes a minimal contribution to parameter understanding.

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: 'Revokes a PENDING invitation', and adds a concrete consequence ('acceptance link stops working'). Clearly differentiates from sibling invitation tools by focusing on revocation rather than creation, reading, or listing.

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?

Provides explicit conditions: only PENDING invitations can be revoked, and ACCEPTED/REVOKED/EXPIRED ones return 404. This gives clear exclusion criteria, though it does not name alternative tools for those cases, so some inference about when to use this tool remains.

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