Feedpeck: RSS Feed Finder & Reader by Website

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: feeds are 'validated by downloading and parsing each one,' output fields are listed, and there is a batch limit of 'Up to 5 sites per call.'

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 sentences with no filler. It front-loads the core behavior and output, then adds the use case and batch constraint, making it efficient and easy to parse.

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?

The description covers what the tool returns, the validation behavior, the use cases, and the call limit. It is complete enough for an agent to invoke correctly, though there is no output schema and no explicit mention of behavior when no feeds are found.

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 fully documents both parameters: 'sites' and 'max_items_per_feed.' The description only reinforces the batch limit already present in the schema and adds no new parameter-level meaning.

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 a specific verb and resource: 'Find the RSS, Atom and JSON feeds a website publishes' and lists what is returned. It is clear about the tool's purpose, though it does not explicitly distinguish from the sibling tool 'latest_posts' by name.

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 gives concrete use cases: 'Use when you need a feed URL for a site or want to know if a site has a feed.' It provides clear context but no explicit exclusions or alternatives, so it stops short of a 5.

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

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds useful context (max 300 char summary, fields returned) but does not disclose any special behavioral caveats like rate limits or failure modes. With annotations present, this level of transparency is adequate but not exceptional.

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?

A single, well-structured sentence packs a clear result list, use cases, and the 'without scraping' advantage. No filler, and the most important information (what is returned) is front-loaded.

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 read-only tool with only two parameters, the description is nearly complete. It names all key fields returned and the summary length cap, which is sufficient for an agent to understand the output. It could be more explicit about error behavior or the exact JSON envelope, but the absence of an output schema is partially mitigated by the explicit field list.

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 documents both parameters. The description does not add any parameter-level meaning beyond what the schema provides; it only reiterates that it reads from the main feed. Baseline 3 is correct since no compensation is needed.

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 precise verb ('Get') and resource ('newest posts of one website from its main feed') and enumerates the exact fields returned (title, URL, published date, author, summary, categories, image). It also lists concrete use cases (blog, news, subreddit, YouTube, GitHub) that distinguish it from a feed-finder sibling, making the tool's scope unmistakable.

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 gives explicit when-to-use guidance by naming target content types and contrasting with 'scraping pages'. It implies the prerequisite of an existing feed, but it does not explicitly say 'if you don't know the feed, use find_feeds first'. Given the sibling exists, a direct mention would earn a 5; the current guidance is clear but not fully explicit.

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