meta_ads_ad_sets_get

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

No annotations provided, so description carries full burden. It explicitly states 'Read-only' and lists the fields returned, including delivery_estimate (if available). This is sufficient behavioral transparency for a simple getter tool, though no details on rate limits or auth requirements beyond implicit Meta Ads account ID usage.

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?

The description is concise (2 sentences) and front-loaded with the core purpose. Lists fields efficiently and includes usage guidance. No wasted words.

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 lists many return fields and notes delivery_estimate conditionally. For a read tool with 2 parameters, this provides complete context for an agent to understand what the tool returns and how to use it.

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%, so baseline is 3. The description adds some context: account_id can fall back to credentials, and ad_set_id is the one to inspect. It does not add syntax or format details beyond the schema, but complements it adequately.

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 ad set, including targeting spec and budget/bidding configuration. It lists specific fields returned, distinguishing it from sibling tools like meta_ads_ad_sets_list (which likely lists ad sets without full details) and meta_ads_ad_sets_update (which modifies).

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 states 'Call this before meta_ads_ad_sets_update when you plan to modify targeting, so you can merge instead of overwrite.' This provides clear when-to-use guidance and references an alternative. Does not mention other alternatives or when not to use, but the specific recommendation is strong.

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