News search (SearXNG)

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

Annotations already cover readOnlyHint and idempotentHint. The description adds a meaningful security warning about untrusted web content and instructions found within it, which is crucial behavioral context not present in annotations. It also mentions the time_range filter, but that is already in the schema. No contradictions with annotations.

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 short sentences with no fluff. It front-loads the core purpose, then adds one relevant filter detail, and closes with a critical security warning. Every sentence earns its place.

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 tool is a read-only search with full schema coverage, an output schema, and comprehensive annotations, the description covers the essential aspects: purpose, key filtering capability, and the security caveat. It doesn't discuss result ordering or pagination nuances, but those are less critical given the schema and output schema. Overall, it is sufficiently complete for an agent to invoke the tool 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 100%, so the schema fully documents all seven parameters. The description adds no additional semantic detail beyond mentioning the time_range filter, which is already described in the schema. Thus the description provides minimal extra value for parameters beyond the schema baseline.

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 states a specific verb and resource: 'Search recent news articles.' This clearly distinguishes it from siblings like image_search, video_search, music_search, and general search by indicating a news-specific resource. The inclusion of 'recent' adds temporal scope, making the purpose unambiguous.

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?

Usage is implied rather than explicit. The description says to search recent news articles, which suggests the tool is for news queries, but it does not explicitly state when to choose this over sibling tools or name alternatives. No exclusions or when-not-to-use guidance is provided.

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