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

With no annotations, the description carries the full burden and does a fair job: it discloses the four outcome states, the verification chain (PoolCreated log, factory poolOf, listing in GET /v1/pools), and that 'pending carries retry_after_seconds', which tells the agent it may need to poll. It omits auth requirements and whether results are cached/eventually consistent.

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 a single dense, run-on sentence with inline URL templates and parentheticals that interrupt the flow. The trigger is front-loaded well, but the structure is crowded and would be clearer split into usage and return-value sentences.

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 5-parameter, no-output-schema tool, the description covers outcomes and lookup modes but leaves the required chain_id and the 'line' enum undocumented, and does not say how to interpret a 'pending' final state (timeout/backoff). It is adequate but has clear gaps.

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 40% (chain_id, line, asset have no descriptions), but the description compensates by clarifying the mutually exclusive lookup modes — tx_hash versus seller+asset — which the schema alone does not express. It still leaves 'line' (layer/v4/v4-glmr) and chain_id semantics unexplained.

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 (pool status after createPool) and enumerates the possible outcomes (pending | created | reverted | no_pool), so an agent knows exactly what this returns. It is clearly distinguishable from siblings like taifoon_pool_open_plan and taifoon_pool_quote, though it does not name them explicitly.

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?

It gives an explicit trigger ('After you broadcast createPool') and names both invocation modes (by tx via /v1/pools/open/{chain}/{tx}, or by seller and asset). This is clear contextual guidance, though it never states when *not* to use it or which mode to prefer in ambiguous cases.

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