WAzion MCP Server

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

Since no annotations exist, description must carry full behavioral burden. It successfully discloses credential fallback logic, but fails to declare safety profile (read-only vs destructive), rate limits, or what specific success/failure responses look like. No contradiction with annotations (none provided).

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?

Front-loaded with specific platforms and purpose. Two clear sentences with minimal waste, though the trailing '[query]' appears to be template noise or artifact that slightly detracts from perfect conciseness.

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 zero-parameter diagnostic tool. Covers platform scope and credential behavior. Absence of output schema means description could ideally summarize return format (boolean vs detailed status), but the core operational context is sufficiently described for agent selection.

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?

Input schema contains 0 parameters (empty object), which warrants a baseline score of 4. The description mentions credential usage 'si no se proporcionan' (if not provided), which aligns with the zero-parameter schema indicating reliance on saved configuration rather than inline inputs.

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 states specific action ('Verifica') and resource ('conexion con la plataforma e-commerce'), listing exact supported platforms (Shopify, WooCommerce, PrestaShop, VTEX). This distinguishes it from sibling 'test_shopify_connection' which is platform-specific, and from 'connect_ecommerce' which establishes rather than tests connections.

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 implicit usage context by describing the credential fallback behavior ('Usa las credenciales guardadas si no se proporcionan'), but lacks explicit guidance on when to use this versus 'connect_ecommerce' or 'verify_ecommerce_write_permission', and does not state prerequisites or exclusion criteria.

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