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

With no annotations, the description carries the full burden and does disclose the most consequential trait: this is a paid call ($0.03 via x402 in USDC on Base or Solana). It also labels the news_context output as a heuristic and flags the payload as data, not advice. Gaps remain — no latency, caching, error behavior for unlisted tickers, or payment-failure handling.

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 price and headline are correctly front-loaded, and every clause names real returned data (needed given there is no output schema). But it is delivered as one run-on sentence with parenthetical nesting, making it dense to parse; a bulleted field list would serve the agent better.

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 complex, paid, multi-source aggregate with no output schema, the description does substantial work by enumerating every returned block including the news heuristic's label semantics. Remaining holes are edge behavior: coverage of the ticker universe, what happens on an unknown symbol, and any staleness/caching guarantees.

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% and the single ticker parameter is fully documented with an example, so baseline is 3. The description adds only one meaningful constraint beyond the schema: "a single stock perp," i.e. one ticker per paid call rather than a list.

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 concrete resource (a perp research card for one ticker) and enumerates exactly which datasets it bundles: spot/session, perp prices on trade.xyz/Aster/Lighter/OKX, gaps, funding/basis, 72h gap history, verdict, token premiums, weekend gaps, news. That is more specific than any single sibling, but it never explicitly states the relationship to get_quote/get_funding/get_gaps/get_verdict, so the agent must infer that this is the aggregate of those.

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 phrase "one-call" plus the price line implies the trade-off (pay $0.03 for the whole bundle vs. call cheap single-purpose siblings), but this is only implied — no sentence says when to prefer this over get_quote or get_verdict, or that lighter endpoints exist for single fields. Usage is inferable rather than stated.

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