recent_feeds

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

Annotations already include 'readOnlyHint: true', so the description does not need to restate safety. It adds that the tool returns feeds with update time and filters, but does not detail ordering or pagination behavior. This is adequate given the annotation coverage.

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 with no wasted words. The key action ('get most recently updated feeds') is front-loaded. 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?

The tool is simple with no required parameters and 100% schema coverage. The description is sufficient for a basic read operation. Minor omission: does not mention that 'recently updated' is based on the feed's last update timestamp, but this is implied by 'most recently updated'.

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 100% coverage with descriptions for all 5 parameters. The description mentions 'optional language and category filters' but adds no additional meaning beyond the schema. Baseline 3 is appropriate.

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 retrieves 'the most recently updated podcast feeds across the entire Podcast Index' with optional filters. This distinguishes it from siblings like 'recent_new_feeds' (new feeds vs updated) and 'recent_episodes' (episodes vs 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 notes it is 'useful for spotting fresh activity', giving context for when to use it. However, it lacks explicit guidance on when not to use or alternatives (e.g., 'search_by_term' for targeted queries).

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