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

With only readOnlyHint=true provided, the description carries the behavioral burden and does so richly: live SEC EDGAR latency warning (seconds per issuer, minutes cold), coverage limits (parsed schedules only, unscheduled issuers named never estimated), data provenance, the leverage-heuristic caveat for by_rating, units, and that caveats ride tool_notes.

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?

It is dense but front-loaded: the resource and outputs lead, followed by units, caveats, coverage, and latency. Nearly every clause earns its place, though the run-on sentences and parenthetical emphases (NOT, only, FREE) are heavier than strictly necessary.

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 two-param, no-output-schema tool, the description is complete: it names the returned aggregations, units, data source, coverage edge cases, latency, and the vision into tool_notes, leaving nothing an agent needs to call it correctly unstated.

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%, so the schema already documents both parameters. The description reinforces the tickers scoping (market-wide vs max 50) but adds little beyond the schema and never mentions by_sector at all, 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 very specific verb+resource: 'scheduled bond/loan maturities aggregated by year,' and enumerates the aggregation outputs (total_by_year, by_rating, top_issuers_by_year, peak_year, concentration). However, it never distinguishes itself from the close sibling get_debt_maturities, so an agent cannot disambiguate the two from the text alone.

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?

It clarifies scoping behavior ('Market-wide when `tickers` is omitted, or scoped to up to 50 tickers'), which is useful context. But there is no explicit when-to-use guidance, no exclusions, and no routing to the sibling get_debt_maturities, so usage is only implied.

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