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

Annotations only declare readOnlyHint=true, so the description carries real weight here and delivers: it discloses the LATENCY profile (live SEC EDGAR fetch, seconds per issuer, minutes for a cold list), the coverage limitation (only companies with parsed schedules), and the explicit refusal to estimate unscheduled issuers. It also flags that by_rating uses a leverage heuristic rather than agency ratings, which prevents a serious misinterpretation.

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?

Front-loads the resource and its outputs, then layers caveats (units, heuristic, coverage, latency) in order of importance. Despite the caps-heavy style and length, every sentence conveys a fact the agent needs and none is padding.

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?

There is no output schema, so the description must describe the return shape, which it does via the named output fields. Combined with units, coverage boundaries, the estimation policy, and latency, an agent has everything needed to call and interpret this correctly.

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 both parameters are already documented in the schema (max 50, omit for market-wide, by_sector default false). The description largely restates this rather than adding syntax or format detail, so the baseline of 3 is appropriate.

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 resource (the corporate debt maturity wall) and enumerates exactly what it returns (total_by_year, by_rating, top_issuers_by_year, peak_year, concentration), so the agent knows precisely what it gets. It does not, however, differentiate itself from the sibling get_debt_maturities, which an agent could easily confuse it with given the near-identical subject matter.

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?

Clearly states the two usage modes: market-wide when `tickers` is omitted, or scoped to up to 50 tickers. This gives the agent an actionable condition for how to call it. It stops short of naming when to prefer it over the sibling get_debt_maturities or when a different tool is more appropriate.

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