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

With no annotations, the description carries the full behavioral burden. It does disclose the shape of the returned data (metrics per chain, ours vs customers, on-chain vs off-chain), which partially substitutes for the missing output schema. But it says nothing about auth requirements, rate limits, freshness, or pagination.

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?

Front-loaded with the core purpose, then the metric list, then the alternative mode. Two sentences with no filler, though the metric enumeration is dense and could be trimmed.

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 read-only metrics tool with no output schema and no annotations, it is adequate: the metric list and mode description together tell an agent what to expect. Missing pieces are default behavior for 'day', authenticity of the endpoint, and any environmental context, leaving it just at the minimum viable level.

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?

Schema coverage is only 50% (day is documented, series is not). The description compensates by explaining that 'series:N gives N days of headlines instead', clarifying both the meaning of N and that it switches the tool's mode. The 'day' parameter adds nothing beyond its schema description, so it isn't fully comprehensive, but it covers the undocumented parameter well.

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?

States a clear verb+resource ('How much went through the coordination layer') and enumerates the specific metrics returned (calls per route/key class, handshakes, gateway λ steps, hires, grades, bridges, fees) plus the breakdown dimensions. It also names the underlying endpoint and the series variant. However, it does not differentiate itself from siblings like taifoon_network, taifoon_landscape, or taifoon_grid_status, which an agent must distinguish on its own.

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 implicitly routes between two modes: default per-route/key-class breakdown vs. 'series:N gives N days of headlines instead'. That is useful mode selection, but it offers no when-to-use guidance relative to the many sibling metrics/status tools, and no prerequisites or exclusions.

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