WAzion MCP Server

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

No annotations provided, so description carries full burden. It successfully discloses mutation behavior via '[mutation]' tag and warns of the destructive nature by stating confirmation is required to execute. Could improve by mentioning if deletion cascades to existing appointments or is reversible.

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?

Efficient single-sentence structure with title-like prefix, em-dash separator, and parenthetical for safety-critical information. No redundant text, though the Spanish language mix doesn't impact scoring for clarity.

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?

Adequate for a 2-parameter deletion tool without output schema. Covers core operation and safety requirements. Missing potential impact context (e.g., whether existing bookings using this service type are affected or if operation is permanent).

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 has 100% description coverage with 'ID del servicio a eliminar' and confirmation instructions. Description reinforces the confirm=true requirement but does not add semantic meaning beyond what the schema already provides, warranting the baseline score for high-coverage schemas.

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?

Uses specific verb 'Elimina' (Deletes) with clear resource 'servicio/tipo de cita del calendario' (calendar service/appointment type). The '[mutation]' tag explicitly categorizes the operation type, distinguishing it from sibling tools like create_calendar_service or update_calendar_service.

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 clear prerequisite instruction '(requiere confirmación: pasar confirm=true para ejecutar)' indicating the confirmation pattern required for execution. However, lacks explicit guidance on when to use this versus update_calendar_service or create_calendar_service alternatives.

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