create_product_feed

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

There are no annotations, so the description carries the full transparency burden. It only says the tool creates a feed and that SFTP setup happens afterward; it does not disclose whether the feed is activated immediately, whether there are side effects on existing feeds, permission requirements, or what the response indicates about success.

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 short sentences with no wasted words. The main action is front-loaded, followed by the key SFTP caveat and a useful pointer to a sibling tool.

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?

For a mutation tool with no annotations, no output schema, and all parameters optional, the description leaves important gaps: how the caller knows the feed was created, how hosted vs SFTP feeds map to the url parameter, and how the ad account is identified. It does give one useful verification pointer via list_product_feeds, but overall it is under-specified.

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 67%, with url and name already minimally described. The description adds merchant-catalog context and SFTP sequencing, which helps, but it does not clarify ad_account_id, the only parameter lacking a schema description, nor the fact that no parameters are formally 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 opens with the exact verb and resource: 'Create a product feed for the ad account (merchant catalog)'. It also disambiguates follow-up work for SFTP catalogs and points to list_product_feeds, so the tool's role is clear even among many feed-related siblings.

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 gives practical guidance: 'For SFTP-fetched catalogs, configure SFTP after' and 'Use list_product_feeds to see existing'. This conveys sequencing and a verification/alternative action, though it does not explicitly state when this tool should not be used versus related feed management tools.

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