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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds the useful framing that results are informational and not a recommendation, which hints at the nature of returned content. It stops short of saying how results are ordered or truncated (limit defaults live only in the schema).

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 tight sentence front-loads the core action and adds one qualifying clause. Nothing is wasted, though the disclaimer tacked on the end could be dropped or made more informative.

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 read-only, well-annotated, fully schema-documented search with no output schema, the description covers scope, filter dimensions and result intent. Ranking/ordering behavior is the only notable omission an agent might want before relying on top results.

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%, so all five parameters are already documented, including enum-like tier values and the layer slug pointer to list_layers. The description only restates those filter concepts in prose, adding no format or combination semantics 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 (find), resource (stocks) and scope (tracked AI universe) with the filter dimensions that define it. It does not explicitly distinguish itself from sibling lookups like get_ticker or the generic search, so an agent must infer that this is the broad universe-scan while get_ticker is a single-symbol lookup.

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 description implies usage by listing filter modes (name/ticker, layer, tier, minScore), which suggests when the tool fits. It never states alternatives or exclusions, e.g. whether to prefer get_ticker for a known symbol or list_layers to discover valid layer slugs before searching.

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