meta_ads_catalogs_get

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

States read-only behavior and lists returned fields. Without annotations, the description covers key behavioral aspects. Moderate additional context on optional account_id fallback.

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?

Two sentences: first defines purpose and outputs, second adds usage context and parameter hints. No wasted words, information-dense.

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 lists return fields. Covers fallback behavior for account_id and provides usage context. Complete for a read-only get tool.

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 description adds valuable details: explains account_id optional fallback and required prefix, and links catalog_id to sibling list output. Goes beyond 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?

Clearly states it fetches the full detail record for a single Product Catalog and lists specific return fields. Distinguishes from siblings like meta_ads_catalogs_list and provides usage context with delete and create operations.

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 advises calling this before meta_ads_catalogs_delete or meta_ads_creatives_create_collection to verify product_count > 0. Gives clear when-to-use and alternative scenarios.

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