show_traffic

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

The parenthetical 'read-only' explicitly communicates that the operation is non-mutating, which is a useful behavioral signal given that no annotations are present. However, the description does not disclose what kind of traffic data is returned, whether counters are cumulative or sampled, or whether the data is live/cached.

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 extremely short and front-loads the core subject, with no filler words. It is concise; the only issue is that it is so minimal it omits contextual details, but that tradeoff does not hurt the conciseness score.

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 absence of an output schema, annotations, and any differentiation from sibling tools, this description provides only a high-level hint of what the tool does. An agent cannot tell what exact traffic statistics are included, what the return shape looks like, or why this tool should be preferred over show_statistic/show_flow.

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 tool has zero parameters and an empty input schema, so there are no argument semantics for the description to clarify. The schema already provides complete parameter coverage, making the lack of parameter-specific detail non-problematic.

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 as 'traffic' and indicates this is a statistics/read-only operationcars, so purpose is recognizable. However, it largely restates the tool name and does not distinguish it from close siblings such as show_statistic, show_flow, or show_clienttraffic.

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 the many related show_* and *_statistic tools. No alternatives, prerequisites, or exclusions are mentioned, leaving the agent without routing signals.

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