batch_backtest

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

No annotations provided. Description adequately describes input parameters but lacks detail on side effects, permissions, or return behavior. Since output schema exists, return format is covered, but mutation or resource implications are missing.

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?

Description is concise with a summary line and structured Args section. No superfluous content, though the Args format could be more compact. Front-loaded with purpose.

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 7 parameters, 0% schema coverage, and presence of output schema, the description covers inputs thoroughly. Missing contextual cues like when to batch vs single backtest, but otherwise 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?

Schema description coverage is 0%, so the description compensates well. Each parameter is explained with examples and context (e.g., placeholders in base_strategy, dict for parameter_grid). However, rank_by options are listed but no formal enum or validation hints.

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?

Description clearly states 'Run a parameter sweep across strategy variations and rank them.' Verb and resource are specific, and the tool is distinct from sibling tools like backtest and optimize_portfolio.

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?

Description implies usage for parameter sweeps but lacks explicit guidance on when to use this over alternatives like backtest (single backtest) or optimize_portfolio. No when-not-to-use or comparison provided.

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