get_stock_news

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

No annotations are provided, so the description must bear full transparency. It only says 'Get latest news' and provides an example, but does not disclose authentication needs, rate limits, the nature of returned data (e.g., headlines, sources), or behavior regarding the limit parameter. Minimal insight beyond the basic action.

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 extremely concise with two sentences: one stating the purpose and one providing an example. No unnecessary words or redundancy. It is front-loaded and 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?

For a simple tool with an output schema, the description provides sufficient context to understand the basic function. It lacks details about return format (e.g., news articles metadata) but is adequate given the output schema's presence. The example aids understanding.

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 description coverage is 0%, so the description must compensate. It provides an example ('get_stock_news("RELIANCE", 10)') which clarifies that 'symbol' is a stock ticker and 'limit' controls count, but does not explicitly define these parameters. The description adds marginal value over the schema's property names and types.

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 states 'Get latest news for a specific stock.' It distinguishes from sibling tools like get_market_news (for market-wide news) and get_sector_news. The example reinforces the purpose.

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 usage for a single stock's news via the example and phrasing, but does not explicitly state when to use this tool versus alternatives like get_market_news or get_sector_news. No exclusions or when-not-to-use guidance is provided.

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