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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety and closed-dataset profile is covered. The description adds genuine context beyond that: it discloses that some fields are conditional ('listing gain once listed') and that the profile comes 'with sources,' telling the agent to expect absent values for pre-listing IPOs. It does not cover behavior on unknown or ambiguous company names, which keeps it from a 5.

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: the verb, resource, and lookup key come first, followed by the payload enumeration. The field list is long but each item is a distinct returned data type, so it earns its place; a bulleted or grouped structure would read slightly better.

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?

With only one parameter, no output schema, and annotations covering the safety profile, the description's field enumeration effectively substitutes for a return-value spec, which is the main thing an agent needs. The remaining gap is behavior when the name matches nothing or matches multiple IPOs, which is left unspecified.

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% and the schema already provides an example ('Jio Platforms'), so the parameter is fully documented structurally. The description reinforces the lookup key as a company name but adds no matching rules, aliases, or ambiguity handling beyond the schema. Baseline 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 and lookup key: 'Everything on one Indian IPO by company name,' then enumerates exactly which data fields are returned (GMP history, price band, subscription buckets, dates, registrar, profile). The 'everything on one IPO' framing implicitly contrasts with the narrower siblings get_ipo_gmp_today and get_upcoming_ipos, so an agent can distinguish scope without opening the schema.

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?

Usage is only implied: fetch a single IPO's full dossier when you know the company name. The description never explicitly says when to prefer this over get_ipo_gmp_today, get_gmp_accuracy, or get_upcoming_ipos, nor does it state any exclusions or prerequisites. Adequate but leaves routing inference to the agent.

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