WAzion MCP Server

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

No annotations are provided, so the description carries the full burden. While the '[mutation]' tag indicates a write operation, the description fails to disclose critical behavioral traits: whether the old URL becomes invalid immediately, if there is downtime during the change, validation rules, or whether the operation 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?

The description is appropriately brief and front-loaded with the action and resource. The em-dash structure separates the action from the explanation efficiently, though the dual phrasing ('Cambiar' vs 'Actualiza') is slightly redundant.

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 this is a single-parameter mutation tool with no output schema, the description meets minimum viability by identifying the operation. However, for a potentially breaking change like updating a store URL, it lacks important context about side effects, redirects, or validation behavior.

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?

The input schema has 100% description coverage for the single parameter (url_tienda), including an example URL. The description adds no additional semantic information about the parameter format or constraints, meeting the baseline for high schema coverage.

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 clearly states the tool updates the online store URL using specific verbs ('Cambiar', 'Actualiza') and identifies the resource (URL de la tienda). However, it does not explicitly differentiate from sibling ecommerce configuration tools like configure_ecommerce_locales or connect_ecommerce.

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 no guidance on when to use this tool versus alternatives, nor does it mention prerequisites such as whether the store must be disconnected first or validation requirements for the new URL.

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