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

There are no annotations, so the description carries the burden of behavioral disclosure. It clearly indicates a data-retrieval operation and details the returned content, but it does not explicitly state read-only behavior, error handling, pagination, locale effects, or any operational caveats. This is adequate but not fully transparent.

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 tool's core purpose and then uses a structured colon-and-list format to enumerate relevant content areas. It is somewhat dense, but every listed item contributes to the agent's understanding of what the prospectus data includes.

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 no output schema and no annotations, the description must do substantial work. It thoroughly describes the returned data, but it leaves usage boundaries, parameter semantics, and behavioral caveats mostly implicit. It is sufficient for selecting the tool but less complete for guiding a cautious 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 0%, so the description must compensate for parameter documentation. It only relates to the stock_code parameter through the phrase 'for a stock' and provides no detail on stock_code format or the locale parameter. The schema property names are self-explanatory, but the description adds little beyond what the schema already shows.

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 clearly identifies the tool as returning 'Full prospectus info page data for a stock' and enumerates the major content areas: offer price, mechanism, greenshoe, subscription tiers, cornerstone investors, IPO financial statements, timeline, directors, syndicate, and stabilizing manager. This is specific enough to distinguish it from sibling tools like get_cornerstone_ranking, get_financial_data, and get_underwriter_ranking.

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 phrase 'Full prospectus info page data' implies the tool is for retrieving a complete prospectus dataset, and the content list gives context on what it covers. However, it does not explicitly say when to use this tool instead of narrower sibling tools, nor does it state exclusions such as 'for just cornerstone rankings, use get_cornerstone_ranking.'

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