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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action and a parameter note, without describing output, side effects, or safety profile. 'Backtest' implies read-only, but that's not explicitly stated, and no details about default behavior or limitations are given.

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 short and front-loaded, with no wasted words. However, it is under-specified for a tool with four parameters and no output schema, trading completeness for brevity. It earns a median score because it is appropriately concise but not sufficiently informative.

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 four parameters, no annotations, and no output schema, the description is notably incomplete. It explains only one parameter, omits output expectations, and provides no context about the strategy logic or how results are presented. This leaves significant gaps for an agent trying to select and invoke the tool correctly.

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. It only adds meaning for `period` (calling it a 'history window' with examples), but leaves `fast`, `slow`, and `ticker` unexplained. The schema already provides enums and defaults for period, so the added value is marginal, and the core parameters remain undocumented.

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 runs a 'trend crossover strategy backtest' with a specific verb and resource. It distinguishes itself from other backtest tools by naming the strategy type, though it doesn't explicitly differentiate from sibling tools like backtest_sma_crossover.

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 no guidance on when to use this tool versus alternatives. No mention of exclusions, prerequisites, or preferred scenarios. Sibling tools include many other backtest strategies, so the lack of usage guidance leaves the agent to guess.

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