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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds meaningful behavior beyond that: the result is rendered inline as an interactive chart, the specific outputs produced (equity curve, drawdown, return/win-rate/Sharpe), and a fallback `summary` field for non-interactive clients.

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?

Front-loaded with the verb and outcome, then the necessary enumerations. The strategy list is long but earns its place because the schema carries no enums; only the client-fallback sentence feels slightly bolted on.

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?

With readOnly annotations covering safety and no output schema, the description does the heavy lifting by describing what is returned (chart, stats, summary fallback). It is close to complete; gaps are symbol format, initial_capital semantics, and any determinism/latency notes.

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 must compensate and largely does: it enumerates all nine strategy values plus valid period and interval values, none of which the schema exposes as enums. It leaves `symbol` format and the `initial_capital` parameter (default 10000) unexplained, so it is strong but not complete.

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 states a specific verb and resource ('Run a strategy backtest and render its equity curve as an interactive chart') and even names the visual outputs (capital growth, drawdown, stats). It implicitly distinguishes itself from backtest_strategy by promising an interactive chart, but it never names that sibling, so the differentiation is left to inference.

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?

There is one concrete usage cue — clients without interactive app support should read the `summary` field — which is a genuine routing hint. However, it never says when to prefer this over backtest_strategy, walk_forward_backtest_strategy, or compare_strategies, nor any exclusions or prerequisites.

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