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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description adds meaningful context beyond those annotations: OAuth scope requirement read:shortlist, the returned content (tickers with dated stored prices), and behavioral boundaries. It does not discuss empty-state behavior or ordering, keeping it shy of a 5.

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?

Three sentences, all front-loaded and purposeful: purpose/return content, auth and usage trigger, then exclusions. Nothing is wasted or buried.

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 parameters and no output schema, so the description carries the return-value burden and does so by naming tickers and dated stored prices. Combined with the auth requirement and usage trigger, an agent has enough to invoke the tool correctly.

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 is 4. There are no parameter semantics to explain, and the description correctly focuses on purpose, auth, and return content instead.

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?

States a specific verb and resource: reading the signed-in user's saved Research Shortlist of stock/ETF tickers with dated stored prices. It also distinguishes the tool from save_research_shortlist and screening tools by clarifying that it does not evaluate a screen, schedule monitoring, or send notifications.

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?

Gives a clear trigger: 'Use after the user asks for their saved research queue,' and useful exclusions around screening, monitoring, and notifications. It stops short of explicitly naming save_research_shortlist as the write counterpart, so it is strong but not fully complete.

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