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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond them: tiered access (no key with a small daily allowance, API key with 100 free calls/month, or $0.005 USDC per call over x402) and an explicit informational-only disclaimer. It does not describe error behavior or what happens when bars span fewer than N minutes, but the added access detail is substantive.

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 functional description is front-loaded in the first sentence, followed by access/pricing and a disclaimer. Pricing detail is longer than an agent strictly needs to invoke the tool, but it is relevant to whether a call will succeed. No filler or tautology.

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 no output schema, the description compensates by enumerating the returned values (high/low/size, breakout state, first breakout, 1x/2x targets), so an agent knows what it will get back. Inputs are fully covered by the 100%-covered schema. The remaining gap is the absence of any routing guidance relative to the backtest sibling.

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 every parameter (bars, minutes, tz, sessionStart, sessionEnd) is already documented in the schema, which sets the baseline at 3. The description clarifies that 'minutes' defines the 'first N minutes' window and that bars must be oldest-first via 'in your bars', but adds nothing for tz or the session start/end parameters. It neither extends nor contradicts the schema.

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?

States a specific verb-and-resource: it computes the opening range high/low/size for the latest session in the supplied bars, plus breakout state, first breakout, and 1x/2x extension targets. The output enumeration makes the tool's job unmistakable. It does not name the closest sibling (backtest_opening_range_breakout), though 'latest session in your bars' implicitly separates current-session analysis from a historical backtest.

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 no explicit when-to-use or when-not-to-use guidance and no alternative is named; the closest sibling, backtest_opening_range_breakout, is never mentioned. The scoping phrase 'latest session in your bars' hints at the appropriate input but leaves the agent to infer the boundary itself. The access/pricing sentences describe authorization, not usage selection.

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