run_backtesting_analysis

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

With no annotations provided, the description must disclose behavioral traits, but it only lists features. It doesn't mention that it may use real market data, how long execution takes, whether it modifies external state, or what the output format is.

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 sentence with no filler, and it is front-loaded with 'Comprehensive backtesting analysis.' However, it is under-specified for the tool's complexity, which makes it less appropriately sized than a description that would include key usage context.

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 the tool has 7 parameters, no output schema, and no annotations, the description is insufficient. It provides no information about return values, data sources, execution characteristics, or how to interpret 'performance metrics,' leaving major gaps for an AI agent deciding to invoke it.

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 coverage is 100% with all 7 parameters described, so the baseline is 3. The description mentions transaction costs and rebalancing strategies, which map to transaction_cost and rebalance_frequency, but it doesn't add any extra meaning or constraint 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 clearly states the tool performs comprehensive backtesting analysis, citing transaction costs, rebalancing strategies, and performance metrics. While it doesn't explicitly name sibling tools, the combination of these features helps differentiate it from alternatives like run_monte_carlo_simulation or stress_test_scenarios.

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?

No guidance is provided on when to use this tool versus siblings such as run_strategy_comparison or run_walk_forward_test. The description lacks context on prerequisites, data assumptions, or scenarios where this tool is preferred.

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