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

No annotations are present, so the description carries the full burden. It discloses the $0.25 cost, the auth options (payment header, bundle_token, free-tier api_key), and the gate behavior: 'Returns a payment requirement until called with...' This is meaningful context beyond the schema. It does not cover rate limits or error behavior beyond the payment gate.

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?

Two sentences with no filler; the cost is front-loaded and the output contents are listed compactly. The second sentence is long but dense, covering auth and gate behavior. Structure is efficient, though the run-on could be split for readability.

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?

The description provides cost, auth routes, and output fields, enough to attempt a call, but leaves ambiguity: it refers to a 'payment header' while the schema exposes a `payment` property, and it doesn't clarify whether parameters are passed as body fields or headers. No output schema exists, so a fuller statement of the success response shape would help. Overall adequate but with key gaps.

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?

With 0% schema description coverage, the description compensates by explaining the role of all three parameters: `payment` header, prepaid `bundle_token`, and free-tier `api_key` (mintable via get_free_api_key). This clarifies that they are alternative authentication methods, which the bare schema does not convey. It stops short of specifying header names or precedence.

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: 'full XLM sentiment report' with enumerated components (Fear & Greed, order-flow imbalance, 24h momentum, directional verdict, live price, arbitrage context). It does not explicitly name sibling tools like get_xlm_sentiment, relying on 'PREMIUM'/'full' to imply differentiation.

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 implies usage by labeling the tool 'PREMIUM: full XLM sentiment report' and pointing to get_free_api_key for minting a key, but it never directly states when to choose this over get_xlm_sentiment or get_xlm_sentiment_history, nor does it provide exclusionary criteria.

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