stat_report

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

No annotations are present, so description carries the full burden. It discloses that the tool combines multiple endpoints and provides default time ranges, which is useful. But it omits any mention of result size, pagination, or performance implications, leaving some transparency 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?

Two well-structured sentences. The first states the purpose; the second delivers the default time ranges. No redundant or filler content.

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 output schema exists and there are no annotations, the description covers the tool's purpose, entity types, and default ranges, which is sufficient for most use. It could be more complete with an explicit statement about start/end interplay or entity-specific notes, but overall it is comprehensive enough.

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 100%, so baseline is 3. The description adds value by explaining the default time ranges associated with each period value, which enriches the semantics of the 'period' parameter beyond the schema's simple type declaration.

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 states the verb 'Fetch' and the resource 'periodic statistics for site, AP, user, or gateway', and distinguishes itself from siblings by noting it combines all stat report endpoints into one tool.

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?

It provides explicit context that this tool combines all stat report endpoints, implying it should be used over individual stat_* endpoints, and gives default time ranges that inform when to use with certain periods. However, it does not explicitly list exclusions or alternatives, so it lacks a definitive when-not-to-use statement.

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