delete_invitationDelete an invitation by its ID. Use this to cancel pending invitations and revoke access in the Polizei admin API.
Elimina una invitación por id.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID de la invitación |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Does not disclose destructive nature beyond verb, no info on irreversibility, permissions, or side effects. Annotations absent, so description carries full burden but fails to provide.
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?
Single concise sentence, front-loaded with action, no redundant words.
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?
Lacks information on return value, error handling, soft vs hard delete, and differentiation from similar operations like rejection. Adequate for trivial tool but incomplete for safe usage.
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 and description both clearly define the 'id' parameter as the invitation ID, leaving no ambiguity.
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 the verb 'Elimina', object 'una invitación', and method 'por id'. Distinct from sibling tools like create, list, reject.
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?
No guidance on when to use delete vs reject_invitation_user or other alternatives. Missing context on prerequisites or consequences.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.