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

With no annotations, the description carries the full burden and does well: it discloses the $0.03 USDC x402 cost, what is returned (including odds semantics and the neutral-bias case for resistance-before-support), and the tf speed/noise tradeoff. It does not cover rate limits, error behavior, or whether the call is read-only, which keeps it short of a 5.

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?

It is a single dense paragraph with zero wasted sentences: purpose first, then contents, then tf semantics, then the neutral-bias edge case, then alternatives and price. Each sentence adds a distinct decision-relevant fact.

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?

No output schema exists, so the description must explain the return, and it does so thoroughly by listing every bundled component and the neutral-bias behavior. With pricing, tf behavior, and sibling alternatives all covered, an agent has everything needed to call it 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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: tf sets both candle size and lookback range (5m=1H to 1w=1Y) and trades speed against noise. It also clarifies that neutral bias changes the odds interpretation, which is a semantic effect tied to the symbol's analysis rather than the raw enum.

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 opens with a specific verb and resource ('Complete trade setup in one call') and enumerates exactly what the bundle contains: signal bias, regime, levels, entry/stop/target/R:R, odds, time-to-target, invalidation, and track record. It explicitly distinguishes itself from get_signal_bias and get_market_regime as the cheaper single-piece alternatives.

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?

It states when to use this tool (when you need the full setup in one call) and when not to (when you only need one piece, use the cheaper named siblings with their prices). It also gives guidance on choosing tf: shorter is faster but noisier, with the lookback mapping.

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