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

With no annotations, the description must carry the behavioral burden. It discloses the output row anatomy (each row names its source, live meter, and state) and the enumerated state vocabulary, which is genuinely useful. It never states that the board is a read-only snapshot, whether rates refresh, or any auth/rate-limit behavior, leaving real gaps for a pricing surface.

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 front-loaded with the core purpose and stays to two sentences, but the first sentence is a dense jargon chain ('MMR twigs and proofs', 'x402 skills', 'n8n instances') that costs readability for an agent with no glossary. Nothing is wasted, yet nothing is easy to parse on first read.

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?

Two optional filters, no annotations, and no output schema, so the description is the sole source of return-value information — which it partly supplies via row anatomy and state meanings. It omits the peg/oracle mechanics (how the GRID rate is sourced) and freshness/authorization details an agent would want before relying on prices.

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 0%, so the description must compensate, and it largely does: 'Filter with group or state' names both parameters, spells out the state values (LIVE, QUOTE_ONLY, RANKED, BILLED_USD, DENOMINATED, PROPOSED), and the category list maps onto the group enum. Only the exact group tokens are left to the schema enums.

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 resource (a board pricing every Taifoon operation in GRID at the oracle's peg) and enumerates the covered categories (Grid kinds, chain RPC, MMR twigs, AI calls, hosting, bridge, x402 skills, coordination, agents), which lets an agent distinguish it from siblings like taifoon_grid_economics or taifoon_pool_quote. The verb is implicit ('priced'), but the scope is concrete and unambiguous.

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 usage instruction is 'Filter with group or state,' which explains parameters rather than when to choose this tool over taifoon_grid_economics, taifoon_offers, or taifoon_pool_quote. No conditions, prerequisites, or alternative-selection guidance are given.

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