affiliate_awin_download_product_feed

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

No annotations are provided, so the description carries the behavioral disclosure burden. It transparently discloses that the tool returns an 'actionable not-enabled envelope' with endpoint shape, credentials, and next steps, making clear it does not actually download files. It lacks explicit details about auth requirements or side effects, but the core non-fetching behavior is well communicated.

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?

Three sentences, front-loaded with the essential purpose, no unnecessary detail. Each sentence adds value: what it does, when to use it, and what it returns.

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?

With no output schema, the description partially explains the return value (not-enabled envelope with endpoint shape, credentials, next steps), which is useful. However, it omits any explanation of how parameters influence the outcome, so the tool is not fully invocable based on the description alone.

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?

Schema coverage is 0% and the description does not explain the four parameters (format, locale, vertical, advertiserId). The enum for format is present in the schema but its practical meaning is not clarified, leaving the agent unable to reason about correct values or whether parameters are required.

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 it returns implementation status rather than performing a download, naming the specific repo context. It distinguishes itself from sibling tools like affiliate_awin_list_product_feeds by focusing on status/implementation rather than listing 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?

Explicitly states when to use: when a user asks to download an Awin product feed and needs to know why the PR does not fetch large files yet. This gives clear context, though it doesn't name alternative tools for actually listing or downloading feeds.

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