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 partially compensates by disclosing return content ('agentes asignados'), but lacks critical behavioral context like read-only safety, rate limits, or what constitutes a valid ID. The '[query]' suffix appears to be an artifact or placeholder adding confusion.

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 clear verb ('Ver') and reasonably concise (two sentences). However, the trailing '[query]' appears to be noise or a template artifact that detracts from 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 single-parameter retrieval tool with no output schema. The description partially compensates for missing output schema by describing return content ('datos completos'), though it could specify the data structure or format.

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 description coverage is 100% ('ID de la cuenta de email'), establishing baseline 3. The description adds no parameter-specific semantics beyond the schema, though the schema is adequately documented.

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 it retrieves detailed data for a specific email account ('Ver detalle de cuenta de email', 'Devuelve los datos completos de una cuenta de correo especifica') and mentions specific returned content ('incluyendo agentes asignados'). It implicitly distinguishes from the plural sibling get_email_accounts via 'especifica', though explicit contrast would strengthen it.

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?

No guidance provided on when to use this versus get_email_accounts (list) or other email-related tools. No prerequisites or conditions mentioned despite being a specific resource lookup that requires a valid ID.

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