read_articles_batch

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

Disclosed rate limiting (5 sec interval), max 5 articles, timeout parameter, failure isolation, time estimate. No annotations, so description fully covers behavioral traits.

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?

Well-structured with sections, front-loaded purpose, concise yet comprehensive. No wasted words.

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 limits, timing, failure behavior, example. Output schema implied, so return details not needed. Complete for a batch read 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 0%, description adds meaning: urls as list of URLs with max 5, timeout with default. Could specify URL format or constraints, but adequate.

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?

Description clearly states batch reading of multiple articles, distinguishes from sibling 'read_article'. Includes typical use flow linking search_news and analysis.

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 outlines when to use: after search_news to get URLs, before analysis. Provides limits (max 5, 5-second interval). Lacks explicit when-not-to-use but context is sufficient.

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