latest_news

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful behavioral details: the list of sources and the sort order. However, it does not disclose result limits, pagination, or how the 'open world' aspect might affect output. Given the annotations, this is adequate.

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, front-loaded sentence with no wasted words. It states the primary action and key attributes efficiently, making it easy to parse quickly.

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 has a complex context object with many optional fields and no output schema. The description fails to explain how these parameters affect behavior (e.g., sector vs company, date, daysBack), nor does it mention any return format or limitations. This is incomplete for an agent to use correctly, especially given the existence of the negative_news sibling.

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% and the description makes no mention of any parameters. It fails to explain the required 'context' object, the 'daysBack' field, or the various optional fields like 'sector', 'country', and 'companyDomain'. The description adds no semantic value beyond the schema.

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 a specific verb ('Retrieves') and a clear resource ('recent news coverage of a company') and names five distinct sources, while noting the sorting by publish date. This clearly distinguishes it from siblings like negative_news or search_company, so an agent can tell when to invoke it.

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 this is the tool for recent news coverage, but it gives no explicit guidance on when to use it versus alternatives such as negative_news or search_company. There is no mention of exclusions or context where a different tool would be more appropriate.

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