WAzion MCP Server

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It successfully indicates this is a mutation operation via the [mutation] tag and discloses the confirmation requirement, but lacks details on deletion scope, cascading effects on agent data, or reversibility.

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 efficiently combines a summary prefix ('Eliminar agente'), the core action, a metadata tag, and the confirmation requirement in a single sentence with no extraneous text. Every element serves a distinct purpose for agent selection.

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 the simple two-parameter structure with full schema coverage, the description adequately covers the critical safety requirement (confirmation) for this destructive operation. However, it omits scope details such as whether the deletion is permanent or affects associated agent records.

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 both the 'id' and 'confirm' parameters, establishing a baseline where the schema carries the semantic load. The description reinforces the confirmation requirement but does not add substantial meaning beyond what the schema already provides.

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 uses the specific verb 'Elimina' (deletes) with the resource 'agente de atencion' (customer service agent), clearly distinguishing it from sibling tools like create_agent, update_agent, or list_agents. The bracketed [mutation] tag further clarifies the operation type.

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 explicit usage guidance by stating that confirmation is required ('requiere confirmación') and specifying the exact parameter value needed ('pasar confirm=true'). While it effectively communicates the safety mechanism, it does not explicitly contrast when to use this versus update_agent or other alternatives.

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