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

With no annotations provided, the description carries the behavioral burden and usefully discloses that this is a pure lookup with no network calls and that results are capped at 25. It does not cover edge cases such as empty results or matching semantics, but it gives the agent meaningful operational context.

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 core action and result set, followed by useful behavioral context and an example input. Every sentence contributes without waste.

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?

For a simple one-parameter lookup with no output schema, the description is largely complete: it identifies the input shape, return fields, result cap, and no-network behavior. Minor gaps remain around empty results and match semantics, but nothing critical is missing for correct invocation.

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 100%, so the query parameter is already well documented. The description adds the notion of a 'name fragment' and an example, but this largely repeats the schema's own description and example.

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 states a specific verb and resource: it takes an IPO name fragment and returns matching Indian mainboard and SME IPOs. It also specifies the result cap and return fields. It does not explicitly distinguish itself from siblings such as ipo-details or ipo-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?

Usage is implied by the input being a name fragment and by the note that this is a pure lookup with no network calls. However, the description does not explicitly say when to use this tool versus check-allotment, ipo-calendar, ipo-details, or listing-gains.

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