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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds two useful operational facts: reads target 'live' state and api_key is optional for keyless reads. It says nothing about rate limits, freshness/latency, or error behavior for the many actions.

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?

Purpose and the account routing are front-loaded, which is good, but the 16-item action enumeration duplicates the schema enum almost verbatim and turns the description into a dense run-on list. It is informative yet padded with content the agent can already read from the schema.

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 13-parameter, 16-action read tool with no output schema and annotations covering safety, the description supplies the domain vocabulary but omits return-shape expectations, pagination behavior, and which actions require api_key versus keyless access. Adequate as a map, incomplete as an operating guide.

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 description coverage is 100%, so every parameter, including the action enum and its per-action applicability, is already documented in the schema. The description's action list restates the enum rather than adding format or semantics (e.g. what a chain id looks like, what 'reason' values exist). Baseline 3 applies.

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 specific verb and resource set ('Reads the live network, the stream and protocol order state') and enumerates the domains it covers (sellers online, RPC health, stuck orders, Lambda Studio, etc.). It also explicitly distinguishes itself from taifoon_account. Because it is a 16-action multiplexer, the single-sentence purpose is necessarily broad, but an agent can still tell what it observes.

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 only routing guidance is 'For your own account use taifoon_account.' The long action list implies when each mode applies but never states prerequisites, exclusions, or which sibling to prefer for overlapping reads (e.g. taifoon_chain, taifoon_demand, taifoon_op). Usage is inferable, not stated.

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