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

With no provided annotations, the description carries the burden of behavioral disclosure. 'Get' implies a read-only operation, and the description lists what the tool returns, but it does not explicitly state non-mutation, authentication needs, rate limits, or caveats about data freshness. The basic behavior is clear, though more transparency would be ideal.

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?

The description is two tight sentences with no filler. It front-loads the core purpose, then enumerates the returned statistics in a scannable list. Every word earns its place.

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?

This is a simple zero-parameter read tool with an output schema present. The description fully explains what the global statistics contain and signals the global scope. Nothing needed to invoke it correctly is missing.

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 has zero parameters and full schema coverage, so there is nothing for the description to explain about parameters. Per the rubric, zero-parameter tools receive a baseline of 4, and the description adds relevant context about the returned fields.

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 specific verb ('Get') and resource ('global Swarm Intelligence statistics'), then lists the exact data returned. This clearly distinguishes it from sibling tools like mt_get_swarm_graph, which would return structural graph data, and moltrust_stats, which appears focused on trust/reputation stats.

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?

The description gives no explicit guidance on when to use this tool versus alternatives. It implies usage through 'global statistics,' but never names conditions, exclusions, or sibling tools, so an agent must infer the right context from the tool name alone.

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