search

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

The description discloses the 14-day time window and the lack of search operators. However, with no annotations, it fails to mention read-only nature, rate limits, or result format, leaving gaps for a non-trivial tool.

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 two concise sentences with no superfluous content. Every word adds value, 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?

Given the lack of output schema and annotations, the description adequately covers purpose and key constraints. However, it omits details about result structure, pagination, and error handling, which would be expected for a search tool.

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%, but the schema's description for 'q' is only an example value. The description adds context that no operators are supported and all terms are required, which improves semantic clarity 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 clearly states the verb 'Search' and the resource 'entire news index from the last 14 days', distinguishing it from sibling tools like news_latest, which likely returns the most recent articles.

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 notes that all terms are required and no operators are supported, but does not provide guidance on when to use this tool versus its siblings (e.g., news_latest, news_source).

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