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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description is free to add data-semantics context – and it does: 'Prices are display-only; constituents have no inferred weights or inherited ratings' prevents an agent from treating the payload as a ratings/weighting source, and 'source freshness' flags staleness as a first-class concern. It stops short of saying what happens for an unknown or delisted symbol.

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 sentences, zero padding: the first front-loads what you get, the second carries the one caveat that changes how the result may be used. Nothing is repeated from the annotations or schema.

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 single-parameter read with no output schema, describing the returned sections is exactly the right compensation, and the caveat sentence covers interpretation. The only gap is failure behavior for an invalid symbol, which matters for an exact-match lookup.

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% and the single parameter already documents case sensitivity, the pattern, an example (SPYon), and where to source it. The description only echoes 'exact', adding no meaning beyond the schema, so the 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?

States a specific verb and resource ('Get an exact Ondo token') and enumerates the payload sections returned: issuer market observations, constituents, freshness, assessment links. 'Exact' distinguishes it from the listing tool, but it does not say how it differs from the adjacent siblings get_ondo_asset_data and get_ondo_asset_stream, which an agent will see right next to it.

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 only implied: 'exact' signals a precise-symbol lookup rather than a scan, and the schema field says to obtain the symbol from list_ondo_assets. The description itself names no alternative, no when-not condition, and no prerequisite flow.

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