show_news

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

No annotations provided, so description carries full burden. It discloses default behaviors (7-day lookback, 10-item limit), single-ticker scope, and summary fields. It does not mention rate limits or read-only nature, but these are implicitly clear. Slight gap on whether results are sorted by time.

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 sentences with no wasted words. Front-loads the core purpose and immediately follows with defaults and alternative. Highly efficient.

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?

Tool has 3 simple parameters and no output schema. Description lists return fields and explains defaults, making it complete enough for correct invocation. Missing detail on result ordering or pagination, but not critical for typical use.

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 already describes all parameters (100% coverage), so description adds limited additional meaning beyond reinforcing defaults. Baseline is 3; no extra depth on parameter values or constraints.

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?

Description clearly states verb ('show recent news'), resource ('company news from Finnhub for a single ticker'), and lists returned fields (headline, summary, source, published timestamp, URL). It also distinguishes from sibling 'get_brief' which aggregates across holdings, ensuring correct tool selection.

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?

Explicitly states default lookback (7 days) and limit (10 items), and provides a clear alternative: 'For news across all holdings in one call, prefer get_brief'. This tells the agent when to use this tool and when to choose a different one.

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