news

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

No annotations are provided, so the description must fully disclose behavior. It explains data returned (articles with tone and brand-safety signals) and the presence of `request_id`, but does not mention authorization, rate limits, or read-only nature. Adequate but not comprehensive.

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?

Four sentences, front-loaded with the core purpose, no redundant words, and each sentence adds value: purpose, parameters, usage context, and follow-up instruction.

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?

Given the output schema exists, the description does not need to detail return format. It covers the main functionality, parameters, and the workflow linked to `report`. Minor omissions like the required `query` field and defaults are not critical but would improve completeness.

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?

With 0% schema description coverage, the description adds significant meaning: it explains `max_results` and `days` explicitly, and implies the purpose of `query` (topic) and the tags (tone and brand-safety signals) which relate to `tone_filter` and `brand_safe_only`. It does not explain default values or allowed enums, but compensates well.

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 action ('Retrieve news articles') and the resource ('about a topic'), and differentiates from sibling tools by mentioning the tone and brand-safety tags and the later use of `report`.

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 explicitly states when to use ('any question about current events or a topic's coverage') and provides a workflow instruction (call `report` with `request_id`). It lacks explicit exclusions but gives clear context.

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