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

Goes well beyond the readOnlyHint annotation: discloses that no snapshot is kept and no as-of date is accepted, that an API token scoped to this endpoint is required, that each call costs 1 request unit, and the meanings of HTTP 429 (daily limit) and 403 (token not permitted). It also warns that an unknown or rejected ISIN returns the text 'Invalid call' with HTTP 200 — a crucial trap an agent would otherwise misread as success.

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?

The purpose is front-loaded in the first clause and the rest is dense, mostly non-redundant operational detail followed by alternative routing. Slight waste in 'Read-only: it does not write data', which restates the readOnlyHint annotation, and the long run of one-line sentences is more list-like than structured.

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 one-parameter, no-output-schema tool this covers nearly everything needed to call it correctly: cost, auth, error codes, and the notable HTTP 200 'Invalid call' failure mode. The only gap is any indication of what the returned bond record contains or its shape, which matters given there is no output schema.

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 schema already documents the single isin parameter with an example, so the baseline is 3. The description adds validation semantics beyond the schema: an unknown or rejected ISIN produces 'Invalid call' with HTTP 200 rather than an error code, which changes how the agent should interpret results.

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+resource: fetch the current bond record for a single bond ISIN, with a concrete example (XS0971721963). It explicitly disambiguates from sibling tools that handle other data domains (fundamentals, general_isin, government, prices), so an agent can choose it without opening the schema.

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?

Explicitly says when to use it ('when you have a bond ISIN and need that bond record') and names four alternatives with the exact condition that selects each: fundamentals for company statements/forecasts on SYMBOL.EXCHANGE, general_isin to resolve names/equity ISINs, government for Treasury/BLS/BoE series, prices for listed price history.

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