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.02 USDC cost on Base, the in-band x402 MCP payment mechanism (_meta path), and that a pass token bypasses per-call payment. It does not describe return shape or rate limits, but the payment/auth behavior is unusually well documented.

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 a category tag and the core deliverable in one compact sentence, followed by payment mechanics. The trailing raw URL is somewhat redundant but plausibly useful as an alternate access path, so it largely earns its place.

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?

For a moderately complex paid market-data tool with no annotations and no output schema, the description covers venue scope, the joined signal, payment mechanics, and an alternate HTTP endpoint. The main remaining gap is the precise return structure and what 'large-print' measures, but the essentials for correct invocation are present.

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 50%: the 'pass' parameter is already described in the schema, while 'symbol' has only an enum with no field description. The description adds the {symbol} path reference and reinforces that the pass skips payment, but does not clarify what 'symbol' represents or add syntax detail beyond 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 compound deliverable: a 'Kraken large-print buy/sell summary ... joined with WaveTrend 4h state', and explicitly scopes it as 'single venue, not on-chain'. This lets an agent distinguish it from on-chain siblings, though it does not directly contrast with close siblings like get_band_dots or get_full_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?

The description characterizes the data ('single venue, not on-chain') but gives no explicit when-to-use, when-not-to-use, or which sibling to prefer. The 'x402' payment note tells the agent it costs money but not why/when to select this tool over alternatives.

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