Create Product Feed

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

Description adds behavioral context beyond annotations: it states the feed will 'automatically sync products from a URL', revealing the ongoing behavior. The return of the new feed ID is disclosed. Annotations already indicate it's not read-only (correct) and not destructive; description aligns and adds value.

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?

Extremely concise: 4 lines, no fluff. Action, parameters listed, return value stated. Every sentence adds value.

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 creation tool with no output schema, description adequately covers purpose, parameters, and return value. Missing some guidance on prerequisites (e.g., catalog existence), but overall sufficient.

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 description coverage is 100%, so baseline 3 applies. The description repeats schema info for all 4 required parameters, adding only minor clarifications (e.g., 'CSV, TSV, XML' for schedule_url). It does not mention the optional response_format parameter, but schema fully covers it.

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?

Description clearly states the tool creates a new product feed for a catalog, with specific verb 'Creates' and resource 'product feed'. It distinguishes from siblings like meta_create_product (creates a product) and meta_list_product_feeds (lists feeds) by specifying the action and scope.

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?

Usage is implied: use when you want to create a product feed. No explicit when-to-use or when-not-to-use guidance, nor mention of alternatives. Siblings exist (e.g., meta_create_product) but no comparative context is provided.

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