meta_ads_feeds_create

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

With no annotations, the description carries full burden. It discloses that the operation is mutating and not automatically reversible, and suggests recording before-state for possible rollback. It also describes the automatic running behavior. Lacks permission requirements but is otherwise strong.

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 informative and well-structured, starting with the main purpose, then behavior, alternatives, and parameter guidance. It is slightly lengthy but each 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?

Given 5 parameters, no output schema, and no nested objects, the description covers the tool's purpose, behavior, alternatives, and parameter guidance. It lacks details on return values beyond feed_id, but is otherwise complete.

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 100%, so the description adds value by providing context on account_id optionality, schedule enum guidance (e.g., HOURLY for fast-moving inventory), and supported feed formats. This enhances understanding beyond the schema.

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 creates a scheduled product feed that imports products from a URL into a catalog and returns a feed_id. It distinguishes from the sibling tool meta_ads_products_add, which is for one-off product additions.

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 explicitly says when to use this tool (for ongoing bulk sync) and when not to (use meta_ads_products_add for one-off adds). It also mentions that feeds run automatically on a schedule and the first run triggers shortly after creation.

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