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

No annotations exist, so the description carries the entire behavioral burden. It does not say whether this is a read-only aggregation, whether the counts cover a time window or full history, or how expensive/current the numbers are.

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?

It is short and front-loaded with the metric list, with no filler. However, it is an unpunctuated fragment without a leading verb or object, which reads like a field caption rather than a tool description.

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?

There is no output schema and no annotations, so the description is the only source of return-value information, and it gives only a partial field list. It omits the time scope, whether the counts are per-account cumulative, and any indication of response shape beyond the four named metrics.

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 there is nothing for the schema or description to disambiguate; the baseline for a 0-param tool applies. The description does usefully enumerate which metrics are included in the payload.

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 names the specific metrics (verdict mix, dialect hit rate, refused-resend, budget-stop counts), which tells an agent roughly what data this surface provides and differentiates it somewhat from error-oriented siblings. But it is a bare noun phrase with no verb or subject, so it never states what the tool actually does (retrieve? compute? aggregate?).

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?

No guidance on when to call this instead of dialect_profiles, error_classify, or error_enforce, and no stated preconditions or exclusions. An agent must infer from the metric names alone that this is a read-only summary path.

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