get_watchlist_brief

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

Annotations already declare read-only and idempotent behavior, while the description adds useful context: the 1-to-20 batch limit, single-request aggregation, Markdown output, and inclusion of a market breadth summary. It does not cover error handling or rate limits, so it is not fully complete.

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 sentences, front-loads the core purpose, and includes only decision-relevant detail. Every sentence earns its place.

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 simple one-parameter read-only tool with strong schema and annotation coverage, the description sufficiently explains its purpose, usage, and return shape. The only minor gap is that 'market breadth summary' is not defined and error behavior is omitted.

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 schema has 100% description coverage and already documents the symbols parameter as 1-to-20 tickers with examples. The description only restates the 1-to-20 limit and adds no syntax or format detail beyond the schema, so the baseline of 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 states a specific multi-ticker batch comparison table, gives the 1-to-20 symbol scope, lists returned fields, and explicitly distinguishes it from single-ticker deep dives. An agent can identify the tool's role 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?

It explicitly says to use this for multi-symbol portfolio or watchlist checks rather than single-ticker deep dives, which gives clear when-to-use guidance. However, it does not name the specific sibling alternatives such as get_quote or analyze_ticker, so routing is slightly less precise.

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