post_downloads_feeds_id_fetch

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

With no annotations, the description carries the full burden. It discloses that the tool performs a remote network fetch and updates the feed, and warns about TTL-based errors. This is transparent for a simple operation, though it doesn't mention auth or rate limits.

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 extremely concise: two sentences and a list of error codes. It is front-loaded with the primary action and adds only essential details. Every sentence earns its place.

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 main action and constraints but omits the return value format or any success response information. Since there is no output schema, this information would be valuable for an agent to parse results. Still, for a simple tool with one parameter, it is minimally complete.

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, and the description does not add any semantic information about the 'id' parameter beyond its implicit meaning from the tool name. No clarification on format, constraints, or allowed values.

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 action: 'Remotely fetches the RSS feed and updates it.' It uses a specific verb and resource, and the error codes further clarify the purpose. It distinguishes from sibling tools like get_downloads_feeds_id (read-only) and post_downloads_feeds (create 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 provides context: it warns about the TTL constraint and lists error codes, implying when the tool can be used successfully. However, it does not explicitly compare to alternatives like post_downloads_feeds_fetch or state when not to use it.

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