fetch_multiple_feeds

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: batch fetching capability and per-feed status reporting. However, it doesn't mention error handling details, rate limits, authentication requirements, or what constitutes 'success' versus 'error' status. The description adds value but leaves important behavioral aspects unspecified.

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 a single, efficient sentence that front-loads the core functionality. Every word earns its place: 'batch' establishes scope, 'fetch multiple RSS feeds' states the action, and 'with success/error status for each' adds crucial behavioral context. No wasted words or redundant information.

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 batch operation tool with no annotations and no output schema, the description provides adequate functional context but lacks important details. It doesn't explain the return format (what does 'success/error status' look like?), error handling behavior, or performance implications of the parallel parameter. Given the complexity of batch operations, more completeness would be beneficial.

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 the schema already fully documents both parameters. The description doesn't add any parameter-specific semantics beyond what's in the schema. It mentions 'batch fetch' which aligns with the urls array parameter, but provides no additional syntax, format, or usage details for parameters.

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's purpose with specific verbs ('batch fetch') and resource ('multiple RSS feeds'), and distinguishes it from siblings by emphasizing batch processing and per-feed status reporting. It explicitly mentions 'success/error status for each' which differentiates it from single-feed tools like fetch_rss_feed.

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 implies usage context (batch processing multiple feeds with status tracking) but doesn't explicitly state when to use this versus alternatives like fetch_rss_feed (single feed) or get_feed_headlines (headlines only). It provides clear functional context but lacks explicit comparison guidance.

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