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

Annotations already establish readOnly and non-destructive behavior, and the description adds meaningful operational context beyond them. It details the transaction classifications, guarantees that terms come from the newest effective prospectus/latest filing and never a superseded document, and states what result content to expect. This is exactly the kind of data-provenance and content disclosure that helps an agent trust and use the tool correctly.

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 description is five sentences long and front-loaded with the core purpose and ordering rule. Each sentence adds a distinct fact: transaction types, document provenance, result contents, filtering, and sibling routing. The filtering sentence slightly duplicates schema documentation, but the overall structure is efficient and scannable.

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?

Given the absence of an output schema, the description does a strong job of telling an agent what each row will contain: lifecycle, proposed listing, offer terms, and latest annual XBRL financials. It also implies CIK is present by instructing the agent to use a row's CIK with GetIpoDetails. Pagination and filter mechanics are covered by the fully described input schema, so nothing critical is missing.

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?

All four parameters have complete descriptions in the input schema, including defaults, allowed lifecycle values, and the SIC-based SPAC distinction for filerType. The description only restates the filtering capability at a high level and does not add new parameter-level semantics. With 100% schema coverage, the schema rightly carries the weight here.

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 a specific resource (US S-1/F-1 registration pipeline), a concrete verb ('Get'), and an ordering rule ('newest filing activity first'). It also distinguishes this list-style feed from GetIpoDetails by pointing detail-seekers to that sibling tool. This is well beyond a tautology and differentiates the tool within a large sibling set.

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 clearly positions the tool as the pipeline/feed endpoint and explicitly routes deeper filing-chain requests to GetIpoDetails using a row's CIK. It doesn't list exclusions for other potentially similar tools such as GetFormDOfferings or ListFilings, so the guidance is good but not exhaustive.

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