get_download_stats

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful behavioral detail that eMule figures appear only when the eMule service is enabled, but says nothing about whether the values are instantaneous samples, cumulative averages, or what units they're in.

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 sentences, zero waste, with the returned metrics front-loaded and the sibling routing placed last where it belongs as a disambiguation clause.

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 zero-param read tool with no output schema, the description covers what comes back (total down/up plus conditional eMule speeds) which is the main thing an agent needs. The missing piece is units/sampling semantics of the returned numbers, but the shape of the response is adequately conveyed.

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?

Zero parameters, so the schema carries no semantics burden and there is nothing for the description to compensate for. Baseline 4 applies.

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?

Uses a specific verb (get) and resource (Download Station throughput statistics) and spells out exactly which metrics are returned: aggregate download/upload speed plus conditional eMule speeds. It also distinguishes the aggregate scope from the per-task view in list_downloads, so an agent can tell it apart from siblings.

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?

Explicitly routes the agent: use this for aggregate throughput, use list_downloads for per-task speeds. Clear usage context, though it doesn't address other plausibly adjacent siblings such as get_download_info or get_resource_usage.

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