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

With no annotations present, the description carries the full burden and it does disclose some behavioral traits: the ordering ('ordered by listing date desc') and the optional year filter. But it omits other operationally relevant details such as data source, result size, pagination, or auth requirements.

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 a single, information-dense sentence that front-loads the key output fields and wraps up with the filter and ordering. The '?year' notation is slightly informal, but overall it is compact and scannable.

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 there is no output schema and no annotations, a short description should still convey what a caller will get back and how the year filter behaves. This description leaves terms like 'hit rate' undefined, does not say how many records are returned, and gives no indication of the output structure.

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 schema has 0% description coverage for the single 'year' parameter. The description adds that it is an 'Optional ?year filter', which is useful, but it does not clarify whether the year applies to listing date, allotment date, or something else, nor what the default 0 means.

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 deliverable ('Oversubscription + frozen capital + hit rate') and a clear scope ('all stocks with allotment data'). However, it does not explicitly distinguish itself from sibling tools like get_allotment_result or get_allotment_tiers, so it stops short of a full 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?

No guidance is provided on when to choose this tool over the nearly-related allotment siblings, nor are any exclusions or alternative tools mentioned. The description only implies a general use case through its scope clause.

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