check_feeds

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

With no annotations, the description carries the burden. It mentions 'Fetches and stores latest items', indicating a side effect. However, it does not disclose potential delays, network usage, whether repeated calls are safe, or any rate limits. It provides moderate transparency but lacks depth.

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 relatively concise but includes sample prompts that are not essential. The structure places purpose first, followed by examples and parameter details. It could be more concise by removing the sample prompts, but it is not overly verbose.

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 the basic operation and parameter. However, given the availability of an output schema (not shown but present), it does not explain what happens if no new items, error handling, or how it interacts with related tools. For a simple tool it is adequate but not comprehensive.

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?

The schema has 0% description coverage, so the description must compensate. It explains the single parameter 'source_type' with a list of valid values (news, reddit, etc.) and the default behavior (empty checks all). This adds meaningful semantics beyond the schema's type string.

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: 'Check all (or specific) subscriptions for new content. Fetches and stores latest items.' The verb 'check' is specific to fetching new items, and the resource 'subscriptions' is clear. It distinguishes from sibling tools like 'get_feed_items' (which likely retrieves stored items) and 'list_subscriptions' (which lists feeds).

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 provides sample prompts that hint at usage but does not explicitly state when to use this tool versus alternatives like 'get_feed_items' or 'subscribe'. No guidance on when not to use or prerequisites (e.g., must have subscriptions).

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