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

Annotations only flag readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false; the description goes well beyond them, disclosing the x402 USDC-on-Base payment challenge, that no payment is auto-spent, that a supplied signature authorizes one irreversible settlement, and that unavailable sections are labeled with a reason plus a coverage field. These are exactly the behavioral traits an agent must know before invoking a paid write-like call.

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?

Strongly front-loaded with the payload then the usage condition, and every clause is information-bearing. There is mild redundancy across the payment clauses ('never auto-spends,' 'nothing is charged,' 'an honest not-available result'), which keeps it from a perfect score, but the paragraph remains tight for the breadth of behavior it covers.

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?

An output schema exists, so return values need not be detailed, and the description instead supplies the pieces the schema cannot: payment flow, failure/not-available semantics, coverage labeling, and a use-case example. For a paid, non-idempotent, open-world tool this is complete enough to invoke correctly on the first attempt.

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%, so the baseline is 3, but the description adds real meaning to payment_signature ('bound to this exact challenge', 'authorizes one paid, irreversible x402 settlement') that the schema's one-line description does not fully convey. The symbol parameter adds little beyond 'one US ticker,' which the schema already covers, so this stops short of 5.

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 verb and resource ('Get a one-call intelligence profile for one US ticker') and enumerates the exact payload sections returned (quote, gamma regime, flow, squeeze score, FTD/Rex SHO, Oracle directive). It distinguishes itself from aggregation alternatives by framing the value as 'a full picture of a stock in a single paid call instead of stitching several sources together.' An agent can tell what this tool produces without opening the schema.

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?

Explicit when-to-use is given ('Use this when an agent needs a full picture of a stock in a single paid call'), the alternative (stitching several sources) is named, and a concrete scenario ('profile GME before writing a research note') anchors usage. The payment path is also conditionally specified: unsigned call returns a challenge, retry only with a challenge-specific payment_signature.

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