ACTION_GET_TRAFFIC

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the returned field names and the snapshot-JSON result format, which is useful, but it says nothing about permissions, whether counters span all SIMs/interfaces, or how the schema's require/on_error behavior interacts with the read.

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?

Three short clauses: purpose first, then output fields, then interpolation/result-format note. Nothing is redundant, though the output enumeration is a dense list that could be trimmed.

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 simple read tool with no output schema, the description covers what is read, the fields returned, and the variable-snapshot result shape. The remaining gap is error/requirement semantics that the schema exposes but the description does not discuss.

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 coverage is already 100%, so the baseline is 3; the description adds a genuinely new cross-cutting fact - that string parameters accept ${var} interpolation - which the schema does not state. It still does not explain output_var/require interactions, so it is not a full 5.

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 specific verb and resource: read the device-wide cumulative RX/TX byte counters since boot. That clearly separates it from neighbors like ACTION_GET_STORAGE_INFO or ACTION_NETWORK_STATUS, though it never names an alternative explicitly.

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 choose this over sibling tools that also report connectivity or device state (ACTION_NETWORK_STATUS, ACTION_GET_SIM_INFO), nor any prerequisite or exclusion. The agent must infer usage entirely from the purpose sentence.

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