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

The readOnlyHint and openWorldHint annotations already establish safety and world-dependence, but the description adds useful behavioral details: it returns every symbol in a specifically bounded universe, includes a count, and excludes scores. This goes beyond the annotations by clarifying the exact output content and scope.

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 two short sentences, with no wasted words. It front-loads the core action ('Every ticker symbol...') and packs in scope, count, and exclusion of scores efficiently.

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 no-parameter, no-output-schema list tool, the description conveys the key output aspects: the full set of covered tickers, the approximate count, and that scores are not included. It is complete enough for an agent to know what to expect, though it does not specify the exact return structure (e.g., separate count field vs. count in the 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 baseline for this dimension is 4 per the rubric. The description appropriately focuses on the output semantics rather than parameters, and no additional parameter information is 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?

The description clearly states the tool lists every ticker symbol in the Gold Silver Analytics free-subset coverage universe (~279), plus a count, and explicitly notes it returns symbols only, not scores. This distinguishes it from siblings like get_rr_score and search_tickers by specifying the resource (all covered tickers) and scope (free subset).

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 when to use this tool (when you need the full list of covered tickers) but does not explicitly name alternatives or state when not to use it. The phrase 'Symbols only — no scores' hints that other tools handle scores, but this guidance is not explicit.

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