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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real value with provenance (median of three public trackers) and refresh cadence (every 30 minutes on market days). It omits any statement about staleness when markets are closed or what happens with zero matches.

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?

Two dense sentences with the core scope front-loaded before the field list and the freshness caveat. Nearly every clause carries information, though the enumeration of output fields is slightly list-heavy for a description without an output schema.

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 no output schema, the description usefully enumerates what comes back (GMP in rupees and %, estimated listing price, subscription, dates, board). Filters are covered by the schema, so the only real gap is behavior on empty results or closed-market days.

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 both parameters are already documented; the baseline of 3 applies. The description glancingly reinforces them by naming 'board (Mainboard/SME)' and 'listing gain' for include_listed, but adds no format or behavior detail 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?

Opens with a specific verb and resource ('Live grey market premium (GMP) for Indian IPOs') and narrows scope to open, upcoming, or awaiting-listing IPOs, with an explicit field inventory. It does not name any sibling, so differentiation from get_upcoming_ipos and get_ipo is left implicit.

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 by the word 'Live' and the state filter; there is no statement of when to prefer this over get_upcoming_ipos or get_ipo. The 'refreshed every 30 minutes on market days' line hints at freshness trade-offs but never routes the agent to an alternative.

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