WAzion MCP Server

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

The description includes the '[mutation]' tag, which helpfully indicates this is a write operation, but this is the only behavioral trait disclosed beyond the basic creation action. Without any annotations provided, the description fails to disclose important behavioral aspects such as permission requirements, reversibility of the creation, idempotency, or error handling behavior. The agent lacks information about what happens if the calendar_id does not exist.

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 front-loaded with the action 'Crear notificacion de calendario' followed by the em-dash explanation, delivering maximum information in minimal space. Every element serves a purpose: the Spanish title fragment, the explanatory clause, the enumerated notification types, and the mutation tag. No redundancy or filler text is present.

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 moderate complexity of six parameters with full schema coverage and no output schema, the description adequately covers the primary purpose and notification variants. However, gaps remain regarding error handling, the return value or identifier of the created notification, and prerequisite conditions (e.g., valid calendar_id). For a creation tool lacking annotations and output schema, additional behavioral context would be necessary for full completeness.

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?

With 100% schema description coverage, the input schema already fully documents all six parameters including their types and purposes. The description lists the notification types in the parenthetical, but this merely echoes the schema's description of the notification_type parameter without adding syntax details, format constraints, or semantic relationships between parameters. Baseline score applies as the description does not compensate beyond the comprehensive schema.

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 the specific verb 'Crea' (Creates) combined with the resource 'notificacion automatica para un calendario', clearly stating the tool's function. It explicitly distinguishes this tool from siblings like update_calendar_notification and delete_calendar_notification by using the creation verb. The parenthetical enumeration of notification types (confirmacion, recordatorio, cancelacion, seguimiento, no-show) further clarifies the scope.

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 lists the specific notification types that can be created (confirmation, reminder, cancellation, follow-up, no-show), providing implicit context about when to use the tool. However, it lacks explicit guidance on when to prefer this tool over update_calendar_notification or delete_calendar_notification, and does not mention prerequisites such as calendar existence. No alternative tools or exclusion criteria are specified.

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