Global statistics

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 does disclose the kind of data returned (speeds and queue counters) plus implicitly that this is a non-mutating read. It says nothing about rate limiting, freshness/refresh semantics, error behavior, or permission requirements, which would be expected given the absence of annotations.

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 front-loaded sentence with no filler or redundancy. Every clause (speeds, queue counters) conveys distinct information about the payload.

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 output schema, the description is the only source of return-value information, and it only names broad categories rather than the actual counters or fields returned. For a simple zero-argument read tool this is workable but not complete enough to tell the agent exactly what it will receive.

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 description to clarify beyond confirming that it needs no input; the baseline for a parameterless tool is 4. The schema is an empty object, which is consistent with the description.

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?

States a specific verb (Return) and resource (aggregate download/upload speeds plus queue counters), which is concrete and immediately actionable. It does not, however, differentiate itself from the sibling aria2_status or aria2_list, leaving some ambiguity about which statistics source to pick.

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 prerequisite context, and no mention of alternatives such as aria2_status or aria2_list despite several overlapping-looking siblings. The agent must infer that this is the global/session-wide stats call from the name alone.

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