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

Annotations declare readOnlyHint=false without explaining why a quote read is non-read-only; the description resolves that by disclosing the $0.005 USDC charge and the x402 challenge-then-retry flow, which is exactly the behavioral fact an agent must know before calling. It also flags the data as delayed. It does not cover rate limits or what a failed/underpaid call returns beyond the challenge.

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, front-loaded with the identity of the tool, then the cost and payment mechanics. The bracketed x402 instruction is dense but every clause carries operational information an agent needs before spending money.

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 paid one-parameter quote call, the description covers what it returns at a high level, what it costs, how to pay, and the HTTP equivalent. With no output schema present, it could say more about the fields in the snapshot, but the gaps are minor relative to what is already disclosed.

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?

The single required parameter is fully documented by the schema (100% coverage), so the baseline applies. The description adds only the framing that the ticker identifies one instrument, plus the HTTP path template; it gives no notation guidance (e.g., exchange suffix) beyond what the schema already says.

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?

"Single-ticker snapshot (delayed quote)" states a specific resource and scope, and the word "single-ticker" implicitly contrasts with the batch sibling screener_screen. It stops short of naming that sibling explicitly, so the agent must infer the split from the name alone.

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?

Usage is implied by "single-ticker snapshot" — use it for one symbol rather than a screen — but there is no explicit statement of when to prefer it over screener_screen, nor any prerequisite or failure guidance beyond the payment handshake.

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