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

Annotations already declare readOnly, idempotent and non-destructive, and the description reinforces this with 'it does not build, sign or send a transaction' and scopes out eligibility. It adds genuine behavioral context beyond annotations by disclosing data limits ('where researched', sourced 'from issuer documentation'), which tells the agent results may be partial. It does not mention latency or data freshness beyond that caveat.

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 opening clause, but the remainder is a single run-on sentence that crams seven or eight parallel content lists into one breath. It is dense and scannable only with effort; breaking the enumerated contents into a short structured list would cost nothing and gain clarity.

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-value shape need not be restated, and the description instead characterizes the substance of the response (purchase path type, gates, ordered steps, guardrails, exit terms). Combined with read-only annotations and fully documented parameters, an agent has enough to decide whether to call it and what to expect.

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% with only two parameters, both documented in the schema itself (ticker with examples, optional amount_usd described as only affecting the approval-step wording). The description adds no parameter-level guidance, but the schema already carries the burden, so baseline 3 applies.

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 states a concrete deliverable: the step-by-step purchase path for one instrument, including KYC gates, issuer route, venues, exit terms, ordered steps and guardrails. It is clearly not a transaction executor, distinguishing it from write tools. It does not name a specific sibling (e.g. find_permissionless_assets or get_product_details) as the alternative, so sibling differentiation is only implied through the phrase 'it does not say who may buy.'

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?

Usage is implied by the enumeration of contents — an agent should call this when it needs the procedure for buying a given ticker. There is no explicit when-to-use/when-not-to-use statement nor a named alternative tool for the related questions it disclaims (who may buy, executing the trade).

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