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 discloses key business logic (numbers 'no recibiran campanas masivas' won't receive mass campaigns) and that blocks are manual. However, lacks technical behavioral details like pagination limits, response format, or rate considerations.

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 purpose ('Ver lista negra'), efficiently combines definition with behavioral context and sibling differentiation in one sentence. Minor deduction for '[query]' at end which appears to be a placeholder or unclear annotation that doesn't add meaning.

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?

For a simple list operation with 2 parameters and no output schema, the description adequately explains the business concept (manual blacklist vs unsubscribes) and implies return value ('Obtiene los numeros'). Would benefit from mentioning pagination behavior, but sufficient for tool 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?

Schema has 100% description coverage ('Filtrar por numero de telefono', 'Pagina de resultados'), establishing baseline of 3. Description contains '[query]' which may allude to search functionality but adds no explicit parameter semantics or format guidance beyond the schema.

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 provides specific verb ('Obtiene' Gets), specific resource ('numeros bloqueados manualmente' manually blocked numbers), and explicitly distinguishes from sibling tools ('distinta de las bajas voluntarias' distinct from voluntary unsubscribes), clarifying this is for manual blocks not opt-outs.

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 contextual guidance by contrasting manual blocks with voluntary unsubscribes, helping the agent select between this and unsubscribe-list tools. Lacks explicit 'when to use' instruction but the differentiation effectively guides usage decisions.

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