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

The description adds meaningful behavioral context beyond the readOnlyHint annotation: it is paid ($0.05 USDC via x402), invalid pairs are rejected before payment, and levels are derived from price history rather than being trade advice. This is useful for an agent deciding whether to invoke the tool and what to expect.

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 dense but front-loaded with the payment requirement and then enumerates the output components in a clear list. It is a long single sentence, but every clause adds relevant information; it could be split into shorter sentences but is not bloated.

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 there is no output schema, the description does a good job listing the return contents. It also covers payment, invalid-pair handling, and the non-advice nature of the output. It does not explain the x402 payment flow or explicitly address sibling-tool overlap, but it is largely complete for invocation.

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 the schema already documents pair and interval well. The description adds no new parameter-level meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 what the tool returns: price levels, supports/resistances, ATR, pivots, Fibonacci, Ichimoku levels, bias, and a long/short plan for a crypto pair. It is specific about the resource and output, though it does not explicitly distinguish itself from the sibling tools like confluence_signal or ichimoku_signal.

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 guidance on when to use this tool versus the sibling tools. It mentions 'Same as GET /levels/{pair}' and includes 'bias from the confluence signal,' but it never says 'use this instead of confluence_signal for a full plan' or provides any exclusion criteria.

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