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

Annotations cover the read-only/idempotent safety profile, and the description adds genuinely useful behavioral context beyond them: authentication modes, per-call x402 pricing, and that signed-in users spend Credits at a catalog price. The payment requirement in request _meta is valuable operational detail. It stops short of rate limits or response shape detail.

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?

Purpose is front-loaded in the first sentence, and the billing/auth paragraph earns its space by covering a real gate to invocation. The Args block is a touch ceremonial for one parameter but not wasteful.

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 an output schema present, return values needn't be described. Auth, payment, and the sole parameter are all covered, so an agent has enough to invoke correctly. Missing only selection guidance relative to the many sibling analysis tools.

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 0% and the single parameter is undocumented in the schema, so the description must carry it. It does: 'symbol: Stock symbol, e.g. "NVDA"' adds type meaning plus a concrete example. Adequate, though it could note format constraints for non-US tickers.

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+resource+scope: a 'full pre-trade risk scan JSON for a stock'. This clearly distinguishes it from generic siblings like analyze_stock, though it does not explicitly name an alternative. Clear but no sibling routing.

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 details billing mechanics (Credits vs x402) but gives no guidance on when an agent should call this tool versus analyze_stock, get_monte_carlo, or get_iv_radar. Usage context is entirely absent.

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