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

Annotations already establish the safe read-only/idempotent profile, and the description adds genuinely useful behavior beyond them: every field carries a primary-source quote and offset (provenance) and headroom is deliberately withheld when definitions cannot be reconciled (a conditional output behavior). These are not restatements of annotations and help the agent trust and interpret results.

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?

Three tight sentences with no filler, front-loaded on the returned content types. Efficient, though slightly clipped into noun phrases rather than explicit action statements.

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, no-output-schema read tool, the description adequately conveys what comes back (instrument/covenant/headroom data with provenance) and notes the withholding caveat. It stops short of explaining the symbol argument or differentiating from credit siblings, but is close to complete for this complexity.

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?

There is one parameter (symbol) with 0% schema description coverage, so the description is expected to compensate but says nothing about it. The symbol parameter is largely self-evident given the domain, but no format or scope detail is added to explain what symbols are accepted.

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 the specific content it surfaces (credit instruments, covenants, headroom, native-currency maturity walls), so an agent can tell it returns structured credit data rather than a quote or screen. However, it never distinguishes itself from sibling credit tools like credit.instrument or credit.screen, leaving ambiguity about which to pick.

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 prerequisites, and no routing to or away from the sibling credit.instrument and credit.screen tools. The agent must infer usage entirely from the content list.

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