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

Annotations already declare readOnly, non-destructive, closed-world, non-idempotent behavior, so the bar is lower. The description adds one genuinely useful trait annotations do not carry: that access requires an x402 payment authorization. However, it gives no cost, credit, rate-limit, or pagination detail, and 'Purchase' sits in tension with readOnlyHint=true (payment vs. pure read).

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?

A single sentence is appropriately sized and front-loaded, so there is no padding to trim. But the one sentence is dense with undefined jargon ('bounded API-authored') and wastes its budget on a mislabeled resource instead of the parameters the agent needs.

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 five-parameter tool with no output schema and no annotation coverage of returns, the description omits return shape, pagination/limit behavior, date-range semantics, and any cost figure. Too much an agent needs in order to call it correctly is missing.

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 description coverage is 0% across five parameters and there are no enums, so the description must carry the burden. It says nothing about symbol_exchange format, the start/end date semantics, the 260-default limit, or the cs_only flag. 'Bounded' is the only vague gesture toward the limit parameter and is not enough.

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 uses the verb 'Purchase' and resource 'instrument classification history,' but the tool name and title say 'indicators history.' That mismatch means an agent cannot tell whether this returns indicators or classifications. The verb also conflicts with the GET-style name, so the purpose is muddled rather than specific.

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?

There is no statement of when to use this instead of the obvious sibling stocktrends_get_indicators_latest, nor any prerequisite/precondition beyond the implicit payment. The agent is left to infer that 'history' contrasts with 'latest' on its own.

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