Chain Simulator

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

The description goes well beyond the readOnlyHint annotation by explaining the Black-Scholes simulation behavior, that the server fetches the current chain, and that the output is a re-priced chain with Greeks. It also discloses parameter semantics like IV shift range (-50 to +50) and sim_dte=0 meaning at expiry.

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?

The description is well-organized with a short purpose statement, a clarifying analogy, a use-case bullet list, an Args section, and a Returns section. Every sentence adds useful information and there is no filler.

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?

Given there is no output schema, the description appropriately states the return as 'The re-priced chain with Greeks at the simulated conditions.' It covers the purpose, expected inputs, and output at a high level. It could specify the chain structure or edge cases, but for a simulation tool with clear annotations and docs, this is quite complete.

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?

With 0% schema description coverage, the description fully compensates by explaining all five parameters, including ticker's server-side chain fetch, sim_price's hypothetical role, sim_dte's expiry interpretation, iv_adjustment's range and example, and expiration's format and default.

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 opens with a specific verb and resource: 'Re-price an options chain at a hypothetical stock price, DTE, and IV shift.' This clearly distinguishes the tool from sibling chain readers like get_options_chain and scenario analyzers like run_scenario_analysis by emphasizing the hypothetical what-if nature.

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 description provides explicit use-case bullets ('What an option would be worth if the stock moves', 'How theta decay reshapes the chain over time', 'IV crush / IV spike what-ifs'). It gives clear context for when to use the tool, though it does not explicitly name alternatives or exclusions.

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