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

readOnlyHint=true already tells the agent this is a safe read with no side effects, so the bar is lower. The description does add real context by defining 'covered', meaning these tickers receive the full QSignals score and the AI strategic analysis, but it says nothing about what the list elements look like (ticker only, name, sector) or whether the count is fixed.

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 short sentences with zero filler; the scope of the list is front-loaded and the second sentence explains why the list matters. Nothing needs to be trimmed or moved.

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?

No output schema exists, so the description is the only place to learn what a returned entry contains, and it doesn't say whether entries are tickers, names, or sector groupings. For a simple read-only enumeration this is a modest, not fatal, gap.

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 no parameters, so the schema imposes no burden. Per the zero-parameter baseline this scores 4; the description correctly adds no parameter discussion because there is nothing to document.

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 uses a specific verb (List) and a precisely bounded resource: 83 curated AI, space, energy and robotics stocks and ETFs. The card is clear about what it returns, but unlike the best examples it doesn't explicitly name a sibling (e.g. get_stock_score or get_all_scores) to explain the boundary between the covered universe and the general score set.

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?

Usage is only implied: because the tickers returned are the ones that 'get the full QSignals score, including the AI strategic analysis', an agent can infer this is the tool to call before get_stock_score. But there is no explicit when-to-use, when-not-to-use, or named alternative.

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