get_upcoming_ipos

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

Discloses the return content (dates, price band, issue size) and scope (NSE). No annotations are provided, so the description carries the full burden. It does not mention any side effects or prerequisites, but for a simple read-only tool, this is adequate.

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?

Single sentence of 15 words, no redundant information. Front-loaded with the action and resource, achieving maximum efficiency.

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 zero parameters and no output schema, the description is fairly complete: specifies exchange (NSE), data scope (upcoming and ongoing), and returned fields (dates, price band, issue size). Lacks mention of output format or ordering but sufficient for agent to use correctly.

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 has zero parameters, so the schema provides no additional meaning. The description fully specifies what the tool returns and the scope (NSE, upcoming/ongoing IPOs), adding all necessary context for an agent to understand the output.

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?

Clearly states the verb 'Get', the resource 'upcoming and ongoing IPOs on NSE', and the specific data returned ('dates, price band, and issue size'). Distinguishes from sibling tool 'get_past_ipos' which targets past IPOs.

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?

Provides clear context by specifying 'upcoming and ongoing IPOs on NSE', implying it is not for past IPOs. However, it does not explicitly state when to use this tool vs alternatives like 'get_past_ipos' or other financial data tools.

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