ipo_calendar

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

With no annotations, the description carries the transparency burden. It discloses the output fields and that no arguments are needed, implying a read-only operation. However, it does not specify data recency, potential latency, or failure behavior, which is a minor gap for a zero-parameter tool.

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 two short sentences plus a concrete example. Every sentence adds value: what the tool does, what data it returns, and how to invoke it. No filler.

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 the zero parameters and the presence of an output schema, the description covers the core usage well. It lists the output fields and gives an example. A minor gap is not specifying the time range for 'upcoming and recent,' but this is not critical for a simple calendar tool.

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?

There are zero parameters, so the baseline is 4. The description explicitly states 'No arguments needed' and the example reinforces that, adding clarity beyond the empty 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?

The description clearly states the tool retrieves upcoming and recent IPOs on NSE, with specific details like company name, price band, dates, issue size, and status. This distinguishes it from other calendar or market data tools, even without naming alternatives.

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 names the resource (NSE IPOs) and includes a usage example, but does not explicitly say when to use it over sibling tools like earnings_calendar or nse_quarterly_results. Context implies it's for IPO event data, but no alternatives are mentioned or ruled out.

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