WAzion MCP Server

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

No annotations provided, so description carries full burden. While it states 'todos los datos' (all data), it omits critical behavioral details: whether export is synchronous/async, output format (JSON/CSV/zip), delivery method, data retention of the export, or if it triggers notifications to the data subject.

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 structure with clear regulatory framing. Minor deduction for the trailing '[query]' tag which appears to be metadata leakage without explanatory value in the description text.

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?

Regulatory context (Art. 15) is well-specified, but given no output schema and no annotations, the description should explain what the export returns (file download, direct data payload, email delivery) to be complete for a GDPR compliance tool.

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% coverage with 'Telefono del cliente' description. The description doesn't add format details (e.g., country code requirements) or semantics beyond the schema, but with complete schema coverage, baseline 3 is appropriate.

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?

Description clearly states 'Exportar datos del cliente' with specific regulatory context 'GDPR (Art. 15 - Derecho de acceso)' which precisely defines the scope as data access/export, distinguishing it from the sibling tool 'gdpr_delete_customer_data' (which would correspond to Art. 17).

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 Art. 15 reference implicitly signals this is for 'right of access' requests versus deletion, but lacks explicit 'when to use this vs gdpr_delete_customer_data' guidance or prerequisites like verification requirements for GDPR requests.

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