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

No annotations are present, so the description carries the full burden of behavioral disclosure. It states an action (list) but does not mention whether this is a read-only operation, whether it requires authentication, or any potential limitations such as pagination or data freshness. The phrase 'tracked IPO stocks' implies a subset but does not explain what 'tracked' means.

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?

A single, efficient sentence that front-loads the purpose and includes the key return fields. No filler or redundancy.

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 list tool with no parameters, the description states the output fields. However, it does not clarify pagination behavior, ordering, whether the list is exhaustive, or how frequently it updates. Given no output schema, a bit more context (e.g., pagination or time range) would round it out, but it is largely sufficient for a basic list.

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, so the schema is trivially complete. The description adds no parameter-specific meaning, but none is needed. Per the rules, a baseline of 4 applies when there are no parameters.

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 clear verb and resource ('List all tracked IPO stocks') and specifies the fields returned (code, name, listing date). It is immediately distinguishable from sibling tools like search_stocks (which implies search/filter) and list_hk_companies (which is broader scope).

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 use this tool versus alternatives. With many sibling tools (search_stocks, get_homepage_stocks, etc.), the description does not mention any exclusions or conditions that would help an agent decide between them.

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