brave_news

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

Without annotations, the description appropriately discloses a key failure mode (503 on challenge pages) and notes that results are from public HTML. However, it omits details on rate limits, authentication, or what 'normalized' means, and doesn't address mutability or side effects.

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 three sentences, front-loaded with purpose, and contains no redundant information. Every sentence adds value, making it concise and well-structured.

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 no output schema, the description covers purpose, source, and a failure mode, but doesn't describe return format or pagination. It is adequate but could be more informative about the structure of results.

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 100%, so the schema already documents all parameters. The description reiterates default country and lang, adding minimal extra meaning. It provides an overview but doesn't enhance parameter understanding significantly.

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 it searches Brave news results and returns normalized results, distinguishing it from general search tools like brave_search. However, it doesn't explicitly differentiate from other news-specific tools like bing_news or google_news.

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 versus alternatives. The description mentions locale defaults but lacks context for when the tool is appropriate or when to prefer sibling tools.

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