system_get_bandwidth_stats

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

No annotations are provided, so the description carries the full burden, and it discloses almost nothing: no auth requirements, no time window, no granularity, no freshness or caching behavior. Only the implicit read-only nature of 'GET' is communicated.

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?

The content is short but is an unstructured route dump that redundantly restates the endpoint path, the tool name, and a tag line, none of which help an agent beyond the name itself. Being brief here reflects under-specification rather than disciplined conciseness.

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 annotations, no output schema, and an undocumented parameter, the definition leaves an agent with essentially no information beyond the tool name. For a stats endpoint in a crowded system_* family, critical distinguishing and parameter details are missing.

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 single parameter 'tz' has 0% schema description coverage and is never mentioned in the description, so an agent gets no signal about timezone formatting or its effect on the returned statistics. This is a clear documentation gap the description should have filled.

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 concrete verb and resource ('Get Bandwidth Stats'), so the agent knows it retrieves bandwidth statistics. However, it is a raw route echo with no differentiation from closely related siblings such as system_get_stats, system_get_http_stats, system_get_stats_digest, or the bandwidth_stats_* family, so selection remains ambiguous.

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 when-to-use guidance, no indication of how this differs from system_get_stats or system_get_http_stats, and no mention of prerequisites or scope. The agent must infer usage entirely from the name.

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