search_news

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

No annotations provided, so description carries full burden. It states the tool returns specific data (titles, summaries, etc.) and implies read-only behavior. Lacks explicit statement of non-destructiveness, authorization needs, or rate limits, but adequate for a search 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?

Two sentences: first explains functionality and return data, second provides usage guidance. Front-loaded, no fluff, every sentence adds value.

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?

Covers core purpose, required parameters, output fields, and usage context. Missing details on result ordering or pagination, but overall sufficient for a search tool with 5 parameters and no output schema.

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 description coverage is 100%, so baseline is 3. Description adds minimal parameter-specific meaning beyond schema (e.g., notes 'Required field: query' but that is already in schema). Does not elaborate on parameter usage or formats.

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?

Clearly states it performs full-text search across a specific corpus (3,500+ editorial crypto articles) and lists return fields (titles, summaries, citations, entity graph). Differentiates from siblings by specifying the corpus and preference over pretraining for recent crypto queries.

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?

Explicitly requires 'query' field and advises preferring this tool over pretraining for recent crypto events. Compares to a general alternative but does not reference specific sibling tools like search_academy.

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