batch_run

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Run an action' without revealing iterative behavior, delays, state cleanup, or error handling. The restore_start_state and delay_ms parameters imply important side effects that the description does not surface.

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 a single, front-loaded sentence that immediately communicates the core purpose. It is concise and free of filler or redundant content.

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 full parameter schema coverage, the tool is a complex batch orchestrator with 7 parameters and no output schema or annotations. The description does not explain the execution flow, cleanup behavior, or how it relates to same-purpose siblings like strategy_sweep, leaving significant gaps for a tool of this complexity.

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 baseline is 3. The description's mention of 'symbols and/or timeframes' maps directly to the symbols and timeframes parameters, but it adds no extra semantic detail beyond what the schema already provides.

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 uses a specific verb ('Run') and clearly identifies the resource ('an action across multiple symbols and/or timeframes'). It distinguishes the tool from single-symbol/timeframe siblings by emphasizing multi-symbol iteration.

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 implies a clear use case—execute an action for many symbols or timeframes—but does not explicitly state when to use this tool over alternatives like data_get_ohlcv or capture_screenshot. There are no when-not-to-use caveats or named alternative tools.

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