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

Annotations already declare read-only and non-destructive behavior, so the description doesn't need to cover safety. It adds valuable behavioral context by explaining that terms come from the newest effective prospectus or latest filing and never a superseded document, and by listing result contents (lifecycle, proposed listing, offer terms, XBRL financials). This goes beyond what annotations provide, though it doesn't mention operational limits like rate limits or pagination.

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 four sentences, front-loaded with the core purpose, and each sentence contributes new information. It is dense but not verbose, effectively covering scope, data provenance, result contents, filtering, and sibling routing without redundancy. It earns a 4 for good structure and conciseness.

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 there is no output schema, the description sufficiently describes the result content (lifecycle, proposed listing, offer terms, financials) and provides filtering guidance, plus routing to GetIpoDetails. For a read-only tool with three optional parameters, this covers what an agent needs to call it correctly, including data selection logic and output variety.

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%, with each parameter (limit, status, filerType) already documented. The description adds minimal parameter-specific detail—it mentions filtering by lifecycle and SPAC vs operating, which aligns with status and filerType, but doesn't elaborate on allowed values or formats beyond the schema. With full schema coverage, a 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?

The description clearly states the tool's purpose: getting the US S-1/F-1 registration pipeline with newest filing activity first. It specifies the resource (US S-1/F-1 registrations), the verb (Get), and differentiates from the sibling GetIpoDetails by explicitly routing users to it for filing chains. The scope and unique behavior are unambiguous.

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 tells users when to use this tool (to obtain the registration pipeline) and explicitly directs them to GetIpoDetails for detailed filing chains using a CIK from this tool. It also notes filtering options (lifecycle, SPAC vs operating), giving clear context for selecting this tool over alternatives.

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