WAzion MCP Server

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It does not indicate whether this is a read-only operation (implied by 'get' prefix but not stated), what data format is returned, or any rate limiting concerns. The trailing '[query]' tag is confusing and unexplained.

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 brief (one line) but contains noise: the prefix 'Actividad de un agente' appears to be a title substitute (since Title is null), and the trailing '[query]' appears to be a formatting artifact or placeholder. The em-dash separator is structurally odd.

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 lack of output schema and the existence of multiple sibling tools with similar purposes (performance, stats, tasks), the description should explain what specific data this returns and how it differs. It does not, leaving agents uncertain about which tool to select for specific use cases.

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%, documenting all three parameters (agent_id, period, days). The description mentions 'agente especifico' which aligns with the required agent_id, but does not clarify the relationship between 'period' and 'days' parameters or provide usage examples beyond the schema definitions.

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 states it 'Muestra la actividad y carga de trabajo' (shows activity and workload) of a specific agent, providing a clear verb and resource. However, it fails to distinguish from siblings like get_agent_performance, get_agent_stats, and get_agent_tasks, which likely overlap in functionality.

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 tool versus the numerous sibling tools (get_agent_performance, get_agent_stats, etc.) or prerequisites for the query. The description does not clarify if this is for real-time monitoring or historical reporting.

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