backtest_pine

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

With no annotations provided, the description carries full burden for behavioral disclosure. It transparently states that execution is 'fully local — transpile + backtest run in-container; nothing leaves the box, no API key' and explains report offloading behavior when results are too large. While it does not cover every edge case (e.g., error handling), it sufficiently discloses key behavioral traits for a backtesting tool.

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 front-loaded with the core purpose and usage guidance, followed by structured details on parameters and behavior. While it is fairly long, every sentence serves a purpose: explaining use cases, operational details, and sibling differentiation. It could be slightly more concise, but it remains efficient and well-organized.

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?

Despite having no output schema, the description clearly explains the return format: a parsed JSON report with summary, trades, applied inputs/overrides, and elapsed seconds. It also covers the offload-to-file mechanism for large reports. Given the tool's complexity with nested objects and multiple parameters, the description provides sufficient detail to understand inputs, operations, and outputs completely.

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 baseline is 3. The description adds meaningful context beyond the schema, such as explaining how 'inputs' and 'overrides' are sent as environment variables and describing the runtime object's role in timeframe semantics and intra-bar simulation. This enhances understanding of parameter usage and behavior.

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 clear verb+resource pair: 'Run a real, deterministic backtest of a PineScript v6 strategy'. It immediately specifies what the tool does and explicitly distinguishes it from the sibling tool backtest_pine_grid by stating 'Use backtest_pine_grid for sweeps.' This differentiation satisfies the highest level of purpose clarity.

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 guidance on when to use this tool: 'prefer this over estimating its trades or P&L by reasoning' and lists concrete example requests. It also states when not to use it by referencing the alternative backtest_pine_grid for sweeps. This offers clear context for tool selection.

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