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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds real context beyond that: it names the upstream sources (Nasdaq IPO calendar, SEC EDGAR) and the kinds of records returned, though it says nothing about freshness windows or update cadence for 'recently' items.

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 front-loaded sentence that packs the data sources and covered fields with no filler or redundancy. Every clause earns its place.

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?

An output schema exists, so return-value detail is not required, and annotations cover the safety profile. The description is nearly complete for a zero-required-param read tool, with only minor gaps around how 'recent' items are defined and how sections affect output.

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 'section' parameter is fully documented with its enum values in the schema, so the baseline is 3. The description's mention of upcoming/priced/filings content loosely mirrors those options but adds no syntax or default-selection guidance beyond the schema.

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 (IPO calendar) with concrete contents: upcoming and recently priced IPOs, price ranges, exchanges, first-day results, plus SEC EDGAR S-1/F-1 filings. This is unambiguous and clearly distinct from siblings like get_market_movers or compare_platforms, which cover unrelated domains.

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?

The description implies coverage of several data categories (upcoming, priced, filings), which maps loosely to the section options, but it never states when to pick this tool over an alternative or which section to choose for a given intent. Usage is only inferable from the enum values.

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