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

Annotations only provide readOnlyHint=true, and the description does not contradict that. It adds useful behavioral context: daily free quotas for anonymous, signed-in, and power users, plus the paid x402/USDC path beyond the limit. It does not cover empty-result or error behavior, but the output schema and readOnly annotation lessen that gap.

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 purpose is front-loaded in the first sentence, and the second sentence packs quota and pricing information compactly. The quota detail is relevant but somewhat dense; still, there is no filler or redundancy.

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 tool with one required parameter, a fully documented schema, an output schema, and a readOnly annotation, the description provides enough information to call it correctly. It explains the purpose, enumerates membership categories, and covers quota/payment behavior, so nothing critical 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% and the input schema already documents the single `symbol` parameter with an example. The description adds only the phrase 'given ticker' and no additional format, case, or usage nuance beyond the schema, so the baseline 3 applies.

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 identifies the tool's purpose: return all stock-screen memberships for a given ticker, including momentum, technical, earnings, theme, and thesis lists. It is specific about the resource and scope, though it never explicitly names a sibling tool or uses an explicit verb like 'find' or 'list'.

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 intended use is implied: when an agent needs every screen a ticker currently belongs to, this is the tool. However, it does not contrast itself with sibling tools such as list_smart_lists, get_smart_list, or get_list_criteria, nor does it say when not to use it.

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