traffic_stats

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds a genuinely non-obvious behavioral trait beyond that: values are zero unless the traffic meter is enabled, which prevents an agent from misreading zeros as real traffic. It omits any retention, refresh, or granularity detail, so it stops at 4.

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?

Two short sentences, zero filler, with the resource and time coverage front-loaded and the caveat placed second. Every clause earns its place.

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?

With no parameters and an output schema present, the description need not explain return values, and the 'zero unless enabled' caveat covers the main interpretive risk. It is complete enough to call correctly, though a note on whether the meter must be toggled elsewhere would close the last gap.

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 per the rubric the baseline is 4. The schema's empty properties object means there is nothing further to disambiguate, and the enumerated time ranges describe the fixed output shape rather than configurable input.

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?

States a specific resource (traffic meter totals) and enumerates the exact time buckets returned (today, yesterday, week, month), so an agent knows precisely what data this yields. No sibling reports traffic data, but the description never explicitly rules alternatives in or out, keeping it just short of a 5.

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 explicit when-to-use/when-not statement or named alternative. The clause 'Zero unless the meter is enabled' implicitly tells the agent when this tool is worth calling and when its output will be meaningless, which is a partial but real usage cue.

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