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

No annotations are provided, so the description carries the full burden. It states the feed is 'machine-readable' and lists event types, but it does not disclose what the response contains, how events are ordered, whether it is paginated, rate limits, or other behavioral details. For a read-only feed, even minimal expectations like 'returns a list of events' are missing.

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 one concise sentence with a parenthetical enumeration of event types. It is not bloated, and the core subject is front-loaded. However, the phrase 'flash-event feed' is under-specified without further elaboration, and the event-type list is potentially confusing without context, so it is not a perfect 5.

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 needs to provide more context to be complete. It does not explain the return format, event field details, how limit interacts with pagination, or the meaning of locale. An agent cannot determine the expected output or call semantics confidently from this description alone.

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 all parameters. It only explains stock_code as a filter, and does not mention limit or locale at all. The default values in the schema are unexplained, and there is no description of what 'limit' limits or how 'locale' affects output. This is incomplete parameter semantics.

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 the tool returns a 'flash-event feed' with a specific list of event types (ipo_launch / allotment_result / listing / inclusion / prediction) and indicates filtering by stock_code. This is a clear verb-resource pairing, though it does not explicitly contrast with sibling tools that retrieve individual event types, so it earns a 4 rather than 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?

There is no guidance on when to use this tool versus the many sibling tools such as get_allotment_result, get_prediction, or get_inclusion_batch. The description only says 'Filter by stock_code' but does not explain when an agent should prefer this aggregate feed over a specific event endpoint, nor does it mention any exclusions or alternatives.

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