show_clienttraffic

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

With no annotations provided, the description carries the behavioral disclosure burden. 'Read-only' usefully signals that no mutation occurs, but it does not describe what statistics are included, whether the output is a snapshot or aggregated, or if the query could be expensive. This is adequate for a trivial no-parameter read but leaves gaps.

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 concise at six words: 'Per-client traffic statistics' conveys scope and 'read-only' conveys safety. Every word earns its place with no filler or repetition.

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?

For a no-parameter, no-output-schema read tool, the description is mostly usable, but it does not situate this tool among the many traffic/show siblings or clarify what 'client' means in this context. The missing relation to alternatives and output expectations keeps it from being fully complete.

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 takes zero parameters, so the schema fully documents inputs and no description compensation is needed. The baseline of 4 applies because there are no undocumented parameters to clarify.

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 per-client traffic statistics and 'read-only' implies a query/show operation consistent with the tool name. It gestures at differentiation from show_traffic by using 'per-client', though the exact meaning of 'client' is not specified.

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 about when to use this tool versus alternatives such as show_traffic, show_statistic, or show_flow. An agent cannot determine selection criteria or exclusions from the description alone.

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