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

With no annotations, the description carries the full burden; it does usefully disclose the shape of the response (dates, price band, lot size, registrar, status URL, phase, listing-day gains), which tells the agent this is a rich read. However, it says nothing about fuzzy fragment matching behavior — what happens with ambiguous or zero matches — nor about data freshness or whether the call is rate limited.

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?

One front-loaded sentence gives the accepted input form and the full return payload, followed by a compact example. Every clause earns its place and there is no filler.

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?

No output schema exists, so the description correctly spends its words enumerating what comes back, which is the main thing an agent needs. For a one-parameter read tool this is close to sufficient; the remaining gap is ambiguity/no-match behavior and sibling routing.

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% and the single 'ipo' parameter already documents 'slug, id or name fragment' with the same example. The description restates that semantics plus an example input, adding only marginal value beyond the 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?

States a specific verb and resource: resolves an IPO slug/name fragment to full public details of an Indian IPO, and enumerates the returned fields. It does not differentiate from the sibling ipo-lookup, which by name sounds like an overlapping lookup operation, leaving the agent to guess which to call.

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 only implied: passing a slug or fragment is described, and an example input is given, so the agent can infer this is the detail-fetch step. There is no explicit when-to-use versus when-not, and no mention of the sibling tools (ipo-lookup, ipo-calendar, check-allotment, listing-gains) that clearly overlap with parts of this payload.

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