meta_ads_ad_sets_get

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

With no annotations, the description carries the transparency burden. It discloses read-only behavior, lists returned fields, and explains that issues_info is non-empty when the ad set is not delivering. This is useful behavioral context, though it omits error handling or permission requirements.

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: the first front-loads the purpose and returns a comprehensive field list; the second gives actionable usage guidance. Zero filler, perfect structure.

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, the description compensates by enumerating return fields and explaining the special meaning of issues_info. It also provides workflow context with the update tool. Slightly incomplete regarding error scenarios, but for a read-only get operation this is solid.

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 description coverage is 100%, with detailed parameter descriptions for ad_set_id and account_id (including format and fallback). The description adds no parameter-specific meaning, but none is needed given the schema's completeness. Meets the baseline for high schema coverage.

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 ad set' with a specific verb and resource, enumerating key fields. This distinguishes it from sibling tools like meta_ads_ad_sets_list, meta_ads_ad_sets_update, and pause/enable.

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 call this before meta_ads_ad_sets_update when modifying targeting, providing rationale (merge instead of overwrite). Names the alternative tool and specifies the context, going beyond generic 'use when you need details'.

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