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

Annotations cover safety and openness, but the description adds genuinely non-obvious behavior: a $0.02 USDC x402 charge per call, live exchange data versus cached snapshots, a possible first-line DEGRADED marker, and a ProofOfSettledOutcome record. That is real added context beyond readOnlyHint/openWorldHint, though nothing is said about rate limits, latency, or error shapes.

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 core value is stated first, which is good, but the sentence is overloaded with implementation artifacts – kind 30120, data/proof_settled_outcomes.jsonl, the agent name – that do little for tool selection and dilute the front-loaded message.

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?

With no output schema, the description must carry return-shape burden; it names the categories of output and the DEGRADED case but not the structure, availability conditions, or how the ticker is passed. Adequate for a one-parameter tool but with clear 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?

There is a single 'task' string parameter with 100% schema description coverage, so the schema already carries the semantics. 'For any ticker' loosely hints at what belongs in the query, but no format, ticker syntax, or example is given.

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 concrete resource set – real-time market data, technical indicators, and sentiment for any ticker – and explicitly positions itself as a broader single-ticker view than the oracle.* SKUs, which lets an agent distinguish it from siblings. The core purpose is clear, though it is buried among settlement and pricing details.

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 comparison to 'any one oracle.* SKU' implies this is the choice for a comprehensive single-ticker view, and the DEGRADED notice tells the agent what happens on failure. However, it never states when to prefer the narrower oracle.price-feed or oracle.sentiment-analysis instead, nor any exclusions.

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