WAzion MCP Server

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

With no annotations provided, the description carries the full burden. It effectively discloses behavioral traits by labeling it as '[mutation]' and warning that it is an 'acción peligrosa' (dangerous action) requiring explicit confirmation. This adequately warns agents of the destructive nature.

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 efficiently structured with no wasted words. It front-loads the purpose, marks the mutation type, and parenthetically includes the critical safety instruction. Every element earns its place in a compact format.

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 has 100% schema coverage, no output schema, and only 2 parameters, the description is appropriately complete. It covers the essential safety-critical information (mutation, confirmation requirement) needed for an agent to invoke this destructive tool correctly.

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 coverage is 100% so baseline is 3. The description adds value by explaining the semantics of the 'confirm' parameter - clarifying that passing true confirms execution of the dangerous action, adding safety context beyond the schema's basic description.

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 uses specific verb 'Elimina' (Deletes) with specific resource 'notificacion automatica de calendario' (automatic calendar notification). It distinguishes from the sibling 'delete_notification' by specifying 'calendario', though it could clarify the difference between calendar notifications and general notifications more explicitly.

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 clear guidance on the confirmation requirement ('requiere confirmación: pasar confirm=true para ejecutar'), explaining how to execute the deletion. However, it lacks explicit guidance on when to use this tool versus siblings like 'update_calendar_notification' or 'delete_notification'.

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