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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description usefully adds the two result cohorts and the ordering (newest filing first), but says nothing about result size, whether the pipeline list can be empty, or staleness of SEBI filing data.

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 sentence that front-loads the primary cohort and then the secondary one, with ordering given last. No filler and no repetition of the title.

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?

For a no-parameter list tool with annotations and no output schema, the description covers what is included and how it is ordered, which is the essential information. It stops short of describing the shape of each entry or expected volume, which would fully close the gap.

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?

The tool takes zero parameters, so there is no parameter semantics to document; baseline applies. Nothing in the description misleads about inputs.

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?

Names a specific resource (Indian IPOs) and precisely bounds it: announced-but-not-yet-opened issues plus mainboard DRHP filers awaiting dates. The two-part scope and the sort order make it immediately distinguishable from get_ipo and the GMP tools.

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 implied by the scope ('not opened yet' vs. already-open IPOs), which is enough for an agent to route correctly in most cases. However, no sibling is named and there is no explicit when-not-to-use statement pointing to get_ipo or get_ipo_gmp_today.

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