ipo_calendar

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

No annotations provided. The description uses 'Get' implying a read operation, but does not explicitly state that it is safe or has no side effects. With no annotations, the description should more clearly indicate behavioral traits like read-only or any constraints.

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?

Extremely concise: three sentences plus an example. Front-loaded with purpose, no wasted words.

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?

Covers the tool's output fields and scope. Output schema exists to document return values. Could add clarity on the time range for 'upcoming and recent', but overall sufficient for a zero-parameter 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?

No parameters exist; baseline score of 4 applies. Description adds no parameter info because none are needed.

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 it gets upcoming and recent IPOs on NSE, listing the specific data fields (company name, price band, etc.). Distinguishes from many sibling tools focused on stocks, funds, or other financial instruments.

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?

Indicates no arguments needed and provides an example call. While it doesn't explicitly state when to use versus alternatives, the self-contained nature and example imply its use for IPO queries. Could improve by noting that for individual stock data other tools should be used.

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