meta_ads_feeds_create

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

Discloses mutation, reversibility via rollback_apply, and automatic scheduling behavior. Supported formats listed. No annotations exist, so description carries full burden; could detail error handling or URL unreachability consequences but is adequate.

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?

Four sentences, front-loaded with purpose and return value, then mutability, behavior, alternative, and formats. No fluff, 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?

No output schema, so description mentions feed_id return. Covers creation, scheduling, formats, and alternatives. Could mention catalog prerequisite more explicitly, but completeness is high given schema richness.

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?

Description adds context beyond schema: account_id fallback, feed_url requirements (HTTPS, public, auth patterns), schedule enum descriptions with use-case hints (HOURLY for fashion, WEEKLY for evergreen), and name uniqueness. Schema coverage is 100%, so baseline is 3; extra guidance elevates to 4.

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 it creates a scheduled product feed that imports products into a catalog from a URL and returns feed_id. It directly distinguishes from sibling `meta_ads_products_add` by contrasting ongoing bulk sync vs one-off product adds.

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 names alternative `meta_ads_products_add` for one-off adds. Describes feed behavior (automatic schedule, first run soon). Lacks explicit prerequisites (e.g., catalog must exist) but catalog_id is required, making it implicit.

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