Get product feed

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered externally, but the description adds nothing on top — it does not say whether the feed is fetched live from the remote source, whether missing feeds error or return null, or anything about latency/auth. It contributes zero behavioral signal.

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?

It is a single grammatical sentence with no filler and is front-loaded, but its brevity reflects under-specification rather than disciplined concision — there is no meaningful content being compressed.

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?

A read-only single-item fetch with no output schema and no annotation detail about returns leaves the agent without any picture of what a 'product feed' object contains or how to obtain a valid feed_id. For a tool in a dense catalog/feed tool family, this is materially incomplete.

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?

One required parameter (feed_id) with 0% schema description coverage, so the description carries the full burden and provides nothing — no identifier format, no hint where feed_id comes from (list_product_feeds / create_product_feed). The parameter name is self-evident, which is the only reason this is not a 1.

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 sentence 'Get a product feed' is a verbatim restatement of the tool name reddit_ads_get_product_feed; it adds no scope, no distinguishing detail versus siblings like reddit_ads_list_product_feeds or reddit_ads_get_catalog. This is the textbook tautology case.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g. an existing feed_id from reddit_ads_list_product_feeds or reddit_ads_create_product_feed), and no exclusions relative to the ~100 sibling tools. The agent must infer everything from the name alone.

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