get_downloads_feeds

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the return value and lists error codes, but does not mention whether the operation is read-only, idempotent, or requires authentication. An output schema exists but the description does not add behavioral context beyond the basic function.

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 sentence stating the purpose, followed by a list of error codes. It is front-loaded with the main action and contains no unnecessary words or fluff.

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?

Given the tool has no parameters and an output schema, the description is fairly complete. It explains what is returned and lists possible errors. However, it lacks contextual details such as whether the operation is idempotent or read-only, and does not mention any ordering or filtering behavior.

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?

There are zero parameters, so the baseline is 4. The description does not need to add parameter info, and the schema coverage is trivially 100%. The description adequately covers the lack of parameters by stating it returns all feeds.

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 'Returns the collection of all DownloadFeed feeds', which is a specific verb ('Returns') and resource ('collection of all DownloadFeed feeds'). This distinguishes it from sibling tools like get_downloads_feeds_id (single feed) and post_downloads_feeds (create).

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 does not provide explicit guidance on when to use this tool versus alternatives. It only states what it returns. The sibling tool list implies that get_downloads_feeds is for listing all feeds, while get_downloads_feeds_id is for a specific feed, but the description itself lacks direct usage instructions.

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