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

Annotations already establish readOnly, non-destructive, non-open-world, and non-idempotent behavior, so the safety profile is covered. The description's one genuinely additive disclosure is 'Purchase', implying the call consumes credits/quota — a real behavioral trait not expressed in annotations and consistent with idempotentHint=false. However, it says nothing about cost magnitude, caching, rate limits, or failure modes when the symbol is unknown, so the disclosure is useful but shallow.

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 action front-loaded ('Purchase API-authored analytical decision context for one instrument'), no filler. It is efficient, though the brevity is partly a symptom of under-specification rather than discipline.

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, 0% parameter descriptions, and no return-value explanation, the description should carry much more load for a 3-parameter analytical tool. It does not say what comes back, how a decision context is shaped, or how to supply the instrument identifier — all critical for correct invocation.

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% and the description compensates almost nothing: 'one instrument' gestures at the symbol parameter but never explains the relationship between symbol, exchange, and symbol_exchange, nor that all three are optional (required: 0) with likely mutual exclusivity. An agent cannot tell from the description whether to pass symbol_exchange or symbol+exchange.

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 the resource ('one instrument') and the general output class ('analytical decision context'), but that phrase is opaque jargon — it doesn't say whether the result is a rating, a signal, or indicator aggregates. It also fails to distinguish this tool from near-siblings like evaluate_portfolio, get_stim_latest, or get_indicators_latest, which an agent must choose between.

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 only guidance is a liability disclaimer ('not investment advice or a trade instruction'), which is framing rather than selection criteria. There is no statement of when to call this instead of evaluate_portfolio, get_selections_latest, or the indicator-history tools, and no prerequisite (e.g., resolving the instrument first via resolve_instrument).

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