system_get_stats

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

No annotations are provided and the description carries no behavioral information at all: no mention of read-only nature, data freshness, scope of aggregation, permissions, or cost. The description is effectively an auto-generated route stub.

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?

It is short, but brevity here reflects under-specification rather than conciseness — every line (route, title, tags) is machine-generated metadata that adds no meaning for an agent.

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 no parameter documentation, the description is the only source of meaning and it provides none. An agent cannot tell what this returns or how it differs from the many sibling stats endpoints.

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 and the schema is empty with 100% coverage, so there is nothing for the description to clarify. Baseline 4 applies when there are no parameters to document.

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 only restates the tool name ('Get Stats') plus the raw HTTP route, which is a tautology rather than an explanation of what statistics are returned. It does nothing to distinguish it from siblings like system_get_bandwidth_stats, system_get_http_stats, system_get_nodes_statistics, or system_get_stats_digest.

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 guidance on when to use this tool, what it covers, or which sibling to prefer for bandwidth, HTTP, node, or digest statistics. The agent is left to guess among a dozen similarly named system_* stats tools.

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