recent_news

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

No annotations provided; description says it returns rows with specific fields but does not mention side effects, data freshness, pagination, or prerequisites. It is partially transparent but lacks depth.

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: first states purpose, second lists output. Front-loaded and concise, though could be more terse.

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 output schema, but description lists output fields. However, it does not explain how to use nested parameters (req object) nor any limitations. Incomplete given the parameter complexity.

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 coverage is 0% and the description does not explain any parameters (market, region, limit, format). The schema has minimal descriptions (e.g., 'e.g., S&P 500'), but the tool description adds no value beyond that.

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 'get' and resource 'most recent news articles across all tracked stocks', and lists output columns. Distinguishes from sibling tools like news_by_ticker by scope.

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?

No guidance on when to use this tool vs alternatives such as news_by_ticker or screener_news. The description implies it is for a broad overview, but does not explicitly state when not to use it.

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