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

Beyond the readOnlyHint annotation, the description discloses paging behavior (max 200 per call), per-tier rate limits (5/10/50 per day), and overage pricing via x402 USDC — exactly the kind of quota/auth/cost context annotations don't carry. It also adds a 'Descriptive, not a recommendation' disclaimer that matters when an agent relays results to a user. Nothing in the description contradicts the annotations.

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 single sentence is front-loaded with the core purpose ('Symbols currently in a stock screen') before moving to paging, disclaimer, and quota/pricing details. Each clause carries distinct information — content type, safety framing, cost model — with no filler. Dense but not bloated, meriting a 4.

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?

The output schema covers return values, all three parameters are fully documented, and the safety profile is annotated. The description fills the remaining operational gaps: paging cap, entitlement tiers, overage cost, and the non-recommendation caveat. No critical information an agent would need to invoke this correctly is missing.

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 coverage is 100%, with limit, offset, and list_id each already documented in the schema, so the baseline is 3. The description adds minor reinforcement ('max 200 per call' mirrors the limit maximum) and its screen examples echo the list_id values, but it doesn't introduce new parameter meaning. Baseline 3 is appropriate.

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 centers on a specific resource and action — 'Symbols currently in a stock screen' — and grounds it with concrete examples (today's earnings, golden-cross buy signals, AI beneficiaries). The word 'currently' plus the content examples distinguish it from sibling tools like get_smart_list_changes and get_smart_list_metrics, and list_smart_lists is referenced as the source of screen ids. An agent can tell what this returns without opening the 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?

The description implies when to call it — to fetch current members of a known screen — and conveys operational constraints (paging, daily allowance), but it never names an alternative or states a when-not-to-use condition. Routing relative to siblings like get_smart_list_changes or get_smart_list_metrics must be inferred from the word 'currently' rather than stated explicitly. Clear context, but no exclusions or alternatives.

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