WAzion MCP Server

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

No annotations are provided, so the description carries the full burden. It discloses what data is returned (tokens/costs per model) but omits safety characteristics (read-only status), pagination behavior, or time zone handling that would help an agent understand operational impact.

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?

Extremely concise single-line description with information front-loaded. However, the '[query]' suffix appears to be metadata or an incomplete thought rather than purposeful content, slightly diminishing structural 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?

Given the presence of similarly-named siblings (get_usage_stats, get_usage_stats_detail) and lack of annotations or output schema, the description should explicitly differentiate these tools. It partially does so by mentioning AI models, but lacks completeness regarding return structure and sibling selection criteria.

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?

With 100% schema description coverage, the baseline is 3. The description adds minimal semantic value beyond the schema—the '[query]' tag hints at filtering capability but doesn't clarify parameter interdependencies (e.g., if 'period: custom' requires 'date').

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 identifies the resource (API usage statistics) and specific scope (token consumption and costs per AI model). It distinguishes from sibling 'get_usage_stats' by specifying AI model granularity, though it could more explicitly contrast with 'get_usage_stats_detail'.

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 siblings like 'get_usage_stats' or 'get_usage_stats_detail', nor any prerequisites or conditions. The '[query]' suffix is cryptic and doesn't explain parameter relationships.

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