get_http_stats

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the '[READ]' tag in the description merely restates structured data and earns no credit. Beyond the endpoint path, the description discloses nothing further — no return shape, freshness, or scope of the HTTP stats.

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 short lines, front-loaded with the resource and backed by the endpoint identifier — no filler or redundancy. The trade-off is that it is terse to the point of being under-informative rather than wasteful.

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-parameter read tool with no output schema, the minimum needed to call it correctly is present (it is safe and takes no args). It is still incomplete because it never says what 'HTTP stats' contains or how it differs from the other stats tools an agent could pick.

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 by the rubric baseline is 4. There is nothing for the description to clarify beyond the empty schema, and it introduces no misleading parameter expectations.

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 verb plus resource ('Get HTTP Stats') and adds the backing endpoint (GET /api/system/stats/http), so the resource is identifiable. However, it makes no attempt to distinguish this from the many sibling stats tools (get_stats, get_bandwidth_stats, get_stats_digest, get_nodes_statistics), leaving scope 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 guidance on when to use this tool rather than get_stats, get_bandwidth_stats, or the other stats endpoints. No prerequisites, exclusions, or alternatives are mentioned, so the agent must infer usage purely from the resource name.

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