meta_ads_catalogs_list

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

Declares read-only nature and lists return fields. No annotations exist, so the description carries full burden. Lacks details on pagination or rate limits, but for a list operation this is acceptable.

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, one per key info: purpose, output, usage guidance. Efficiently front-loaded with no fluff.

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, but description enumerates return fields (id, name, etc.) and connects to surrounding workflow. Could mention pagination limits but not critical for average use.

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%, but the description adds meaningful context: explains the business_id requirement and optional account_id with fallback behavior. The leading 'act_' prefix clarification is helpful.

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 lists Meta Commerce Catalogs with specific return fields and directly distinguishes itself from sibling tools like meta_ads_catalogs_get/delete by positioning itself as a prerequisite to find catalog IDs.

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 instructs to use this tool to find a catalog_id before calling meta_ads_catalogs_get/delete or managing products/feeds, providing clear when-to-use context and downstream dependencies.

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