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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=true, covering the safety profile, so the description's added value is the failure surface: 'routable (false + error if either token's price can't be resolved)' and the invariant that entryPrice is never overwritten by a live quote. It stops short of describing latency, caching, or chain-specific resolution behavior, which matters for an open-world price fetch.

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 distinction (live price derivation vs. manual), followed by the usage condition and the return deltas. The parenthetical rationale about not overwriting entryPrice is slightly discursive but earns its place by preventing a plausible caller error; overall still efficient.

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?

With no output schema, the description compensates by naming the returned deltas (currentPrice, baseSymbol, quoteSymbol, routable) and the error condition. Combined with 100% schema coverage and read-only/open-world annotations, an agent has everything needed to call it correctly.

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 the schema already documents all 10 parameters including entryPrice as 'manual - a historical fact'. The description reinforces why entryPrice stays manual and clarifies that currentPrice is derived rather than an input, but adds no new syntax, units, or default guidance beyond what the schema/enums already provide. 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 concrete verb+resource (fetches each token's current live USD price and derives currentPrice as their ratio) and explicitly frames itself as the live variant of workflow.run_impermanent_loss, which is itself in the sibling list. An agent can distinguish it from both the non-live variant and unrelated workflow tools without opening a schema.

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?

Gives an explicit selection condition: 'Use when the caller has the pool's two token addresses but doesn't already know the current price ratio.' It also contrasts behavior with workflow.run_impermanent_loss (manual price supplied there, derived here), effectively naming the when-not case.

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