get_stock_news

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the basic function, without mentioning article ordering, date range, error handling, or response structure. The word 'latest' hints at recency but adds minimal transparency.

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 a single, short sentence that front-loads the verb and resource. Every word earns its place; no redundant or vague content exists.

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 low-complexity tool with clear schema and no annotations, the description covers the essential purpose and parameter hints. However, without an output schema, it could briefly mention the return format or behavior when no news is available to be more complete.

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?

Both parameters have detailed descriptions in the schema (symbol: 'Stock ticker symbol'; limit: 'Number of articles to return (default: 10)'). The tool description only restates 'stock symbol' and adds no extra meaning for limit, so the schema carries the semantic load as expected.

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 uses the specific verb 'Get' and identifies the resource as 'latest news articles for a stock symbol.' It clearly distinguishes from sibling tools that focus on economic indicators, technical analysis, or financial statements, none of which cover news.

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 the tool is for retrieving stock-related news, but provides no explicit guidance on when to use it versus alternatives, nor any exclusions. Given the clear purpose, usage is reasonably inferred, but explicit context is missing.

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