meta_ads_catalogs_get

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

With no annotations, the description correctly labels the tool as read-only and details the return fields. It does not mention side effects or rate limits, but for a simple fetch, this 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?

Two sentences with a clear structure: purpose, return fields, read-only flag, and actionable usage. No unnecessary text.

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?

List of returned fields compensates for missing output schema. Usage guidance adds context for downstream tasks. Lacks error handling or auth details, but these are not critical for a read operation.

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?

The input schema has 100% coverage for both parameters, with descriptions included. The description adds value by noting that catalog_id comes from meta_ads_catalogs_list, providing context 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 the tool fetches a single Product Catalog and lists the specific fields returned. It distinguishes from sibling tools like meta_ads_catalogs_list and meta_ads_catalogs_delete by specifying it returns a full detail record.

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 creating a Collection creative, providing actionable context. No explicit exclusions, but the read-only nature and typical usage are clear.

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