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

With no annotations, the description carries the full burden and does so well: it discloses that the returned tx is UNSIGNED, that it is simulated via eth_call + eth_estimateGas, that creating a pool is permissionless and deposits nothing (gas only), and that Moonbeam pools return closed_by_policy. These are exactly the behavioral traits an agent cannot infer from the schema.

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?

Dense but front-loaded — the verb, endpoint and return shape come first, then simulation, permissions, and the follow-on call. Every clause carries information, though the run-on structure could be broken for scanability.

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?

No output schema exists, yet the description explicitly enumerates the return payload { to, data, value, chainId } plus gas, fee and resulting pool address, and covers the state-exists and closed_by_policy branches. Complete enough for an agent to call and handle the result.

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 75% and already documents from/default, line defaults, asset default, seller formats and chain IDs. The description adds genuinely new semantics: the mainnet pool-rule requirement and the override: true escape hatch, tying a parameter to a conditional behavior.

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+resource ('Open a coverage pool behind a seller') plus the exact endpoint (POST /v1/pools/open) and the returned artifact, which cleanly distinguishes it from siblings like taifoon_pool_status and taifoon_pool_quote.

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?

Explains the follow-through workflow explicitly — sign and send with your own wallet, then call taifoon_pool_status with the tx hash — and notes the mainnet pool-rule/override condition. It does not contrast against taifoon_pool_quote, but the context for when to reach for this tool is clear.

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