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

readOnlyHint=true already establishes this is a safe read, so the description's job is to add context beyond that. It does: it discloses the version stamp returned on every response, the exposure tags included, and that the call is free (a cost signal useful for agents optimizing quota). It stops short of describing pagination or response size, which for a 'list every asset' call would be worth knowing.

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?

Two sentences, front-loaded with what is returned and followed by the single action instruction. The parenthetical enumeration is dense but every element is load-bearing, and there is no redundant restatement of the title.

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 input parameters and no output schema, the description carries the full burden of describing the return value, and it does: asset ids, class, name, exposure tags, and universe version. It also states the free cost profile, so an agent has everything needed to call and consume this tool.

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 takes zero parameters, so per the rubric the baseline is 4. The description correctly implies there is nothing to configure — it is a whole-universe dump — which matches the empty 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?

The description names a specific verb (list) and resource (every asset id the service scores), then enumerates the covered classes (top-100 US equities, indices/ETFs, 15 crypto, commodities, FX, rates) and the returned fields. An agent can distinguish this from siblings like exposure_graph or regime_snapshot without opening a schema.

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?

It gives explicit sequencing guidance: 'Call it once to map your tickers to asset ids before using the other tools.' That tells the agent when this tool is appropriate relative to the rest of the set, though it doesn't state exclusions or conditions under which re-calling is warranted.

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