get_dpi_stats

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only implies a read operation via 'Get' and adds nothing about aggregation scope, what the statistics measure, whether data is live or historical, or ordering semantics. It does not contradict any annotation because none exist.

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?

A single sentence with no wasted words, front-loaded with the core verb and resource. It is appropriately compact for a one-parameter tool, though the brevity partly stems from under-specification rather than deliberate efficiency.

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?

The tool is simple (one optional parameter, no nested objects), but with no output schema and no annotations, the description leaves gaps: it does not clarify what qualifies as 'top applications' (by bytes, flows, blocked traffic?), the aggregation granularity, or how it differs from get_client_dpi. Minimal adequate for the simplest agent use, but thin against a large sibling set with overlapping DPI/statistics tools.

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% for the single optional limit parameter, which is already documented as 'Number of top applications to return (default: 10)'. The description adds no parameter meaning beyond the schema, so the baseline of 3 applies.

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 a clear verb ('Get') and resource ('DPI statistics for applications'), so an agent knows what the tool retrieves. The phrase 'for applications' hints at an aggregate scope that distinguishes it from get_client_dpi in spirit, but it does not explicitly name or differentiate from any sibling.

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?

There is no guidance on when to use this tool versus alternatives like get_client_dpi, get_bandwidth_stats, or get_deep_dive. No when-to-use conditions, exclusions, or alternative routing are mentioned, leaving the agent to infer selection purely from the name.

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