system_get_http_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 of behavioral disclosure, and it discloses nothing. It does not say whether the call is read-only (implied but unstated), what scope of stats is returned, whether results are cached, or whether authentication/privileges are required.

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 the three lines are boilerplate: the endpoint path merely re-encodes the tool name and the 'Tags: System Controller' line is internal metadata. Nothing useful is front-loaded, so brevity comes from omission rather than efficiency.

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, no annotations, and no parameters, the description is the only source of information about this tool and it provides none. An agent cannot tell what the returned stats look like or when this endpoint is worth calling.

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 per the baseline rule there are no parameter semantics to document. The empty schema leaves nothing ambiguous, and the description neither helps nor harms here.

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 'Get HTTP Stats' essentially restates the tool name system_get_http_stats, adding only the raw endpoint path and a controller tag. It gives no sense of what 'HTTP stats' actually contains (request counts, latency, error rates) and does nothing to distinguish it from siblings like system_get_stats, system_get_bandwidth_stats, or system_get_nodes_statistics.

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 call this tool versus the many other system/stats siblings. No conditions, prerequisites, or alternatives are mentioned anywhere in the description.

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