Latest bond quotes

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description is free to add value elsewhere — and it does, disclosing unit conventions and the null/'no_data' behavior for a side with no active quote. This is meaningful context beyond the annotations, though batch/rate behavior is not addressed.

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 dense sentence with zero filler: the core purpose is front-loaded, followed by units and then null handling. Every clause carries information an agent needs to interpret the result.

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 correctly carries the return-value burden by enumerating bid/ask, price units, size units, YTM, YTW, and null semantics. This is close to complete, though it does not describe the overall response shape (e.g. per-ISIN grouping) in detail.

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 100% and the single 'isins' parameter (1-100) is fully documented in the schema, so the baseline of 3 applies. The description adds no syntax or format detail about the ISIN input beyond what the schema already provides.

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 a specific verb and resource ('the latest best bid and ask per bond by ISIN'), making the operation unambiguous. The 'bond' scope implicitly distinguishes it from market_latest_quotes and options_latest_quotes, though it never explicitly differentiates itself from those siblings.

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 when-to-use guidance, no mention of alternatives, and no stated prerequisites. The agent can infer it fetches quotes for a list of ISINs, but nothing tells it when this tool is preferable to market_latest_quotes or other quote tools.

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