finstack-mcp

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

With no annotations provided, the description carries the full burden. It discloses what data is returned (company name, price band, dates, issue size, status), which is helpful. However, it omits other behavioral traits like whether data is real-time vs cached, rate limits, or read-only nature that annotations would typically cover.

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?

Four well-structured sentences with zero waste: purpose declaration, output specification, parameter guidance, and usage example. Information is front-loaded and every sentence earns its place.

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 tool's simplicity (zero parameters) and the existence of an output schema, the description is appropriately complete. It usefully enumerates the returned fields even though the output schema technically covers this, providing redundancy that aids agent comprehension.

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, which establishes a baseline of 4 per scoring rules. The description confirms this with 'No arguments needed,' providing appropriate guidance that aligns with the empty input 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 opens with a specific verb ('Get') and clearly identifies the resource (upcoming and recent IPOs) and scope (NSE). It effectively distinguishes from siblings like 'earnings_calendar' or 'nse_quote' by focusing specifically on IPO calendar data.

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 explicitly states 'No arguments needed' which is critical for a zero-parameter tool, and provides a clear usage example. While it lacks explicit 'when-not-to-use' guidance, the specific IPO focus makes the appropriate context obvious compared to sibling tools.

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