get_ipo_calendar

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered without the description. The description adds the returned column set, but this overlaps with the existing output schema, so the incremental behavioral value is modest.

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 front-loaded with the purpose, then cleanly separates Args and Returns sections. It is appropriately sized for a two-parameter read tool with no wasted prose, though the Returns line is redundant given the output schema.

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 an output schema present, return values need not be spelled out, and the annotations cover behavior. The purpose and both parameters are documented, leaving only usage routing to siblings as a gap, which is minor for a simple calendar read.

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 description coverage is 0%, so the description must carry the parameter burden, and it does explain both 'days' (look-ahead window with default 14) and 'limit' (max IPOs with default 25). The meaning is added, though the defaults merely restate what the schema already encodes, keeping it short of a 5.

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?

States a specific verb+resource ('Get upcoming IPOs') and enumerates the returned fields (exchange, expected date, price range, shares), so the tool's scope is immediately clear. It does not explicitly differentiate itself from calendar-like siblings such as get_earnings_calendar, get_economic_calendar, or get_splits_calendar, so it falls short of a 5.

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?

There is no when-to-use or when-not-to-use guidance and no alternative named. It simply states the action, leaving the agent to infer that this is the tool for forward-looking IPO data rather than an IPO history or split-related endpoint.

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