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

With no annotations, the description carries the full burden, and it does disclose key traits: evidence is 'actual' bars, the x402 price is consumed, and no orders are executed. What it omits is material for an agent: whether the call is read-only, whether it incurs the x402 charge itself, what happens on insufficient evidence, and whether WAIT is a valid return rather than an error.

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 tight sentences with the substance front-loaded; the exclusions and sibling pointer are packed efficiently. The dense noun stack ('full-terminal x402 price', 'observed structure and input receipt') costs some readability but nothing is padding.

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 does useful work by listing the return artifacts (bars, typed reasons, structure, receipt) and the refusal boundary. It still leaves the one input undefined and does not clarify the cost/auth implication of the x402 price it depends on, which is significant for a paid decision endpoint.

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 one required parameter (symbol) with 0% schema description coverage, and the description never mentions it. An agent gets no guidance on ticker format, market/exchange qualification, or case sensitivity.

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 concrete outputs (daily/hourly bars, WAIT/SETUP reasons, observed structure, input receipt) and frames the tool as a decision workspace rather than a scanner. However, 'evidence-gated equity decision workspace' is opaque jargon and the verb+resource pair is never stated plainly, so an agent must infer that this returns an analysis/decision for a symbol.

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?

It routes the agent to x402_contract for current pricing terms and gives a negative boundary ('No order execution or profit probability'), which is genuinely useful. It never states when to prefer this over quant_snapshot or mirror_projection, and no prerequisite for obtaining the x402 price is spelled out.

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