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

Beyond the readOnly/idempotent annotations, the description discloses cost per tier, daily free quota, the need for an active subscription or x402 payment_header, the PAYMENT_REQUIRED error case, and the billing outcome in the response. It also clearly separates the pricing tier (detail_level) from the response shape (detail).

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 long but organized: overview, source sources, parameter meanings, pricing, and workflow. It front-loads the core outcome before going into details. The dense parentheticals are hard to scan, but every sentence contributes real information.

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 tool with pricing tiers, required payment mechanisms, and multiple detail modes, the description covers the critical decision points: cost, subscription, response shape, billing outcome, and workflow placement. An output schema exists, so lack of full return-value listing is acceptable; the main completeness gap is the missing behavior of the timeframe parameter and caller_id.

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 descriptions are absent (0% coverage), and the prose partially compensates by explaining assets, detail_level, detail, payment_header, and wallet-related focus. However, timeframe and caller_id are not explained at all, so an agent still cannot fully interpret all parameters from the text.

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 names a specific resource ('crypto market briefing'), a clear verb ('Returns'), and the intended content (market summary, sentiment regime, Fear & Greed reading, source attribution). It also differentiates the tool from the large sibling set by positioning it as the 'INTELLIGENCE step' that frames detect_regime and allocation.

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 gives explicit workflow guidance: 'INTELLIGENCE step (usually first)' and points to get_trading_workflow for broader context. It also explains when to choose 'free', 'pro', or 'platinum' detail levels, so an agent can decide based on cost and need.

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