uisp_get_site_statistics

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

With no annotations, the description must carry the behavioral burden. It discloses that the tool retrieves upload/download traffic in buckets and that it is a read-style operation, but it does not describe response contents, units, or any limitations such as time ranges. This is adequate but not rich.

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?

A single sentence that front-loads the action and the key constraints (parent site, interval bucketing). Every word earns its place; there is no fluff.

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 two-parameter read, this is close to complete, but the lack of an output schema and annotations means the description should say more about return units or response shape. It also does not disambiguate against the sibling summary tool, leaving some selection ambiguity.

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 schema already fully documents both parameters, but the description adds value by clarifying that siteId denotes the site whose traffic to its parent site is being measured. The interval bucketing is also implicitly tied to the interval parameter, slightly enriching the schema.

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 uses a specific verb and resource ('Get upload/download traffic between a site and its parent site') and states the key detail of interval bucketing. It is clear, but it does not explicitly differentiate itself from the closely named sibling uisp_get_site_traffic_summary.

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?

The description makes it clear when this tool is relevant (when interval-bucketed traffic between a site and its parent is needed), but it provides no explicit guidance on when to choose it over uisp_get_site_traffic_summary or other statistics tools. Usage is implied by the purpose rather than stated.

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