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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered; the description adds the return payload (class, name, exposure tags, universe version) and the 'stamped on every response' versioning behavior, which is useful. It omits any note on result size or pagination, but for a static reference list that is minor.

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 list of covered classes is front-loaded effectively, but the trailing 'Free. Use to list valid asset ids for other tools (free).' restates both the zero-cost point and the usage note already made earlier, adding redundancy that dilutes the definition.

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, the description carries the burden of describing returns and does so adequately (class, name, exposure tags, universe version). It is complete for a no-arg reference tool, though it does not state approximate universe size or response format for downstream parsing.

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?

Zero parameters and 100% schema coverage, so the baseline is 4 and there is nothing for the description to compensate for. It correctly implies no arguments are needed.

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 (List) and resource (every asset id the service scores) and enumerates the covered classes, so an agent can distinguish it from data-retrieval siblings like price_for or exposure_graph. The scope and output payload are concrete.

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?

Explicitly instructs the agent to 'Call it once to map your tickers to asset ids before using the other tools', which is a clear prerequisite workflow and distinguishes it from all siblings. No exclusions are given, but for a free lookup tool none are plausibly needed.

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