search_news

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

With no annotations, the description carries all burden for behavioral disclosure. It indicates a read operation (search) but says nothing about result format, pagination, rate limits, or any side effects. Minimal transparency beyond the obvious.

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 very short and front-loaded, but it is under-specified. It lacks essential details like parameter behavior and expected output, making it more sparse than appropriately concise.

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 search tool with no output schema and no annotations, the description is incomplete. It doesn't explain return values, usage context, or any special behaviors, leaving the agent with minimal information to invoke it correctly.

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 0% and the description mentions no parameters. The parameter names (query, max_results) are self-explanatory, but the description fails to add any meaning or explain constraints that the schema doesn't cover.

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 tool searches news articles via SearXNG, with a specific verb and resource. It implicitly differentiates from siblings like search_web and search_images by focusing on news, though it doesn't explicitly name them.

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 on when to use this tool instead of search_web or search_images. The description only states the function and provides no context, exclusions, or alternatives.

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