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

With no annotations, the description carries the burden and does it well: it discloses the 50-row cap, newest-first ordering, the returned fields, and even the date window embedded in the default phase. Only pagination/cursor behavior beyond the cap is unstated.

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 phase options and default are front-loaded, and every clause conveys something useful. It runs a bit long as a single sentence, but no sentence is wasted.

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 compensates by listing returned fields (dates, price, lot size, allotment-check page) and row limits. Complete enough to call correctly; only truncation/pagination behavior past 50 rows 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real value beyond the enum by defining the default's semantics (allotment dates from 2 days ago to 7 days ahead) and giving a concrete example input.

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 gives a specific verb and resource ("Takes a phase and returns up to 50 Indian IPOs") plus the exact phases enumerated. It implicitly distinguishes itself from siblings by scoping to batch listing rather than single-IPO detail/lookup, though it never names the alternatives explicitly.

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?

It clearly explains the default phase and what each phase means, which signals when the tool applies. However, it offers no explicit routing guidance versus check-allotment, ipo-details, or ipo-lookup, leaving the agent to infer which sibling to pick.

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