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 return content (profile details and permissions) but fails to mention safety profile (read-only vs destructive), pagination behavior, or performance characteristics. The '[query]' fragment suggests filtering capabilities not reflected in the schema.

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?

Brief and front-loaded with the purpose, but the trailing '[query]' appears to be metadata leakage or noise that reduces clarity without adding value. Otherwise efficiently structured.

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 list tool, mentioning the return content (profile and permissions) to partially compensate for the missing output schema. However, lacks pagination details or scope limitations despite claiming to return 'all' agents.

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 establishes a baseline score of 4 per the scoring rules. No parameter semantic information is required or provided.

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?

States specific verb (Listar/Lista) and resource (agentes), clarifying scope includes all business agents with profile details and permissions. However, the appended '[query]' is confusing given the empty parameter schema and slightly undermines clarity.

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 no guidance on when to use this versus sibling tools like get_agent_permissions, get_agent_activity, or list_agents_json. No mention of prerequisites, filtering limitations, or exclusions.

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