get_news

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

No annotations are provided, but the description adds several behavioral specifics: limits range from 1-30, each article includes title, summary, publisher, publish time, and URL, and symbol must be a native Yahoo ticker. It does not cover error handling or rate limits, but the disclosed output structure is valuable.

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?

Three succinct sentences with the tool's purpose first, followed by input constraints and output composition. No redundant details or filler.

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 news retrieval tool with an output schema, the description covers purpose, input restrictions, limit behavior, and return fields. It even redirects non-ticker inputs to search, making it self-sufficient for an agent.

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 both parameters with 100% coverage, but the description adds crucial distinction that symbol is not ISIN/WKN and gives concrete examples (AAPL, SAP.DE). It also clarifies 'up to limit' semantics, going beyond the schema's min/max/default.

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?

Clearly states verb 'Get recent news headlines' for a Yahoo symbol, distinguishing it from sibling quote/estimate/financial tools. The description also differentiates from 'search' by deferring symbol resolution.

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 tells users to call 'search' when they have an ISIN, WKN, or company name instead of a native ticker. This direct alternative guidance is missing from many tool descriptions.

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