get_news

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

No annotations exist, so the description must disclose behavioral traits. It does not mention that this is a read-only operation, any authentication requirements, rate limits, or what 'recent' means (e.g., last 24 hours, last week). The term 'recent' is vague and lacks precision.

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, compact sentence with no superfluous words. It is concise and gets straight to the point, which is appropriate for a simple tool.

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?

The tool is simple with one parameter and no output schema, but the description does not hint at the return format (e.g., list of headlines, articles with links) or define 'recent'. These omissions leave some ambiguity, but the basic purpose is clear.

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 100% with a clear parameter description ('Stock ticker symbol.'). The tool description adds no extra meaning beyond what the schema provides, which is acceptable given the simplicity. It neither enhances nor detracts from parameter understanding.

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 the verb 'Get', the resource 'recent news articles', and the target 'a stock'. It distinguishes this tool from sibling tools that retrieve specific financial data like prices, balance sheets, or earnings.

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 is provided on when to use this tool over alternatives. With 18 sibling tools, the description should specify contexts (e.g., 'Use this to get market sentiment or breaking news') or exclude cases (e.g., 'Not for historical news analysis').

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