tastytrade_create_backtest

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

With no annotations, the description carries the disclosure burden and does meaningfully reveal that no brokerage orders are placed, which is a non-obvious and important behavioral trait. Still, it does not mention whether the backtest is executed asynchronously, how long it may take, or what the response represents.

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 two short sentences with no filler. It front-loads the action and resource, then immediately states the key caveat, making it easy for an agent to parse quickly.

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?

The description is adequate for a thin API wrapper, especially with sibling names like tastytrade_get_backtest and tastytrade_cancel_backtest hinting at the lifecycle. However, it does not explain what the tool returns or that the backtest may run asynchronously, which would help an agent know how to poll or retrieve results.

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?

There is only one parameter and the schema already describes it thoroughly as the raw POST /backtests request body. The tool description itself adds no parameter-level guidance, so it stays at the baseline for full schema coverage. The provider-native note in the schema is helpful but is already part of the structured input definition.

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 clearly states the action ('Create') and the resource ('a tastytrade historical options backtest'), so the core purpose is unambiguous. It also adds a research-only qualifier that helps separate it from trading/order tools, though it does not explicitly differentiate from the sibling tastytrade_create_spx_spread_backtest.

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 phrase 'This is research-only and does not place brokerage orders' gives a useful boundary for when not to use it, implying it is for study rather than execution. However, it provides no explicit guidance about when to choose this tool over alternatives like tastytrade_create_spx_spread_backtest or tastytrade_simulate_trade.

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