meta_ads_audiences_get

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

The description declares the tool as 'Read-only' and lists return fields with conditional fields (rule for rule-based, pixel_id for WEBSITE). While no annotations exist, it provides essential transparency. Lacks mention of error conditions or rate limits, but 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?

Three sentences, no fluff. Front-loads the purpose, lists return fields, and concludes with usage guidance. Efficient and well-organized.

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 two simple parameters and no output schema, the description covers the input and output adequately. It mentions all relevant return fields. Could briefly note that it's only for Custom Audiences, but inferred.

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% with good parameter descriptions. The description adds value by stating 'audience_id' is returned by 'meta_ads_audiences_list' and that 'account_id' falls back to environment variable, 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 it fetches the full detail record for a single Custom Audience, listing specific fields returned. It distinguishes itself from sibling tools like 'meta_ads_audiences_list' by focusing on a single audience with full details.

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 to call this tool before 'meta_ads_audiences_delete' or 'create_lookalike' to verify the correct audience. This gives clear context for when to use this tool over alternatives.

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