meta_ads_catalogs_get

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

Declares read-only nature, which is the key behavioral trait. With no annotations, this is crucial. Could add more on permissions or error conditions, but sufficient for a simple get operation.

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 precisely cover purpose, output, and usage context. No redundant information, front-loaded with core action.

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 no output schema, description explains return fields and provides explicit usage context. Sufficient for an agent to understand when and how to invoke the 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 covers 100% of parameters with descriptions. Description adds value by listing the specific fields returned, which goes beyond schema. However, parameter details are already well-covered in 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 'Fetches the full detail record for a single Product Catalog' and lists specific fields returned. Differentiates from siblings like meta_ads_catalogs_list and meta_ads_catalogs_delete by specifying pre-usage contexts.

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 guides to call before delete or collection creative creation, referencing sibling tools. Provides clear context for when to use, though does not exhaustively list when not to use.

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