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

Annotations already establish a safe read-only, non-destructive profile, and the description adds substantial context beyond them: coin settlement, max loss equals flat total premium paid, max profit dominated by the put leg as price falls, and null-valued max fields meaning unbounded. It also enumerates the returned fields, which is valuable given there is no output 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, opening with what is computed and leading into the straddle/strangle distinction. The example phrasings and return-field list are useful, though the single long paragraph is text-heavy and could be broken up; no sentence is truly wasted.

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 enumerating return fields (combinedIntrinsicCoin, scenarioPnlCoin/Usd, breakevens, max loss/profit, isStraddle, isProfitable) and explaining the payoff model. For an 8-parameter computation tool, nothing essential is missing.

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 already high (88%), so the baseline is 3, but the description adds real meaning: quantity is 'both legs sized equally', putStrike must be <= callStrike, and the callStrike === putStrike rule defines a straddle vs strangle. It adds interpretation of premium semantics ('between the strikes, both legs worthless') beyond the field-level docs.

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: computes payoff, P&L, and both breakevens for a straddle/strangle at a scenario price. It explicitly contrasts itself with sibling workflow.run_options_payoff and defines straddle vs strangle via strike relationship, so an agent can distinguish it without opening the 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 clear when-to-use context with concrete user-phrasing examples ('what does a BTC straddle pay off if price barely moves?', 'where are my breakevens on this strangle?'). It references the closest sibling (run_options_payoff) as the coin-settlement analogue, but does not state explicit when-not/to-use-instead conditions versus other payoff tools like run_spread_payoff.

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