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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered without the description's help. The description adds the meaningful detail that metrics are aggregated over rolling windows rather than being a snapshot, but says nothing about window lengths, refresh cadence, or cost/latency of the call — all relevant for a metrics endpoint.

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?

A single front-loaded sentence that names the domain first and then enumerates metric families. No filler, no restatement of the title, nothing to cut.

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 an output schema present and annotations covering read-only/open-world behavior, the description only needs to establish scope, which it does. The one residual gap is that 'rolling windows' is never sized (e.g. 1m/5m/1h), and since there are no parameters the agent cannot discover the granularity at call time.

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 there is nothing for the description to disambiguate; baseline 4 applies. The description doesn't claim or imply any filtering knobs, which is consistent with the empty schema.

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?

Names the specific resource (Ironflow performance) and enumerates the concrete metric families — API latency, error rate, ingestion lag, synthetic probe timings — over rolling windows. This clearly separates it from point-in-time siblings like get_status and get_status_history, though it never names those siblings explicitly to make the contrast airtight.

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 phrase 'over rolling windows' hints at monitoring use, but the description gives no explicit when-to-use, when-not-to-use, or alternative (get_status vs get_status_history vs get_status_metrics is never adjudicated). An agent must infer routing from the description alone, which is a real gap given three similarly named siblings.

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