meta_ads_excluded_placements_get

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

No annotations are provided, so description takes on the burden. It discloses read-only nature, exact return fields, and that unset facets are reported as empty arrays. It doesn't cover error scenarios or authorization requirements, but for a simple read operation this is strong coverage.

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, front-loaded with purpose, followed by return-value details and usage guidance. Every sentence is functional, no filler.

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?

For a simple two-parameter read tool with no output schema, the description fully covers what the agent needs: what it returns, how unset fields are presented, when to use, and how it relates to sibling operations. The schema covers parameters competently.

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?

Input schema covers 100% of parameters with detailed descriptions for both ad_set_id and account_id, including example format and fallback behavior. The tool description itself adds no extra parameter-level information, staying at 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?

Description uses specific verb 'Reads' and identifies resource 'one ad set's delivery-surface exclusions from its targeting spec.' It also distinguishes from sibling tools by explicitly naming meta_ads_excluded_placements_set and meta_ads_analysis_placements.

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 when to use: before meta_ads_excluded_placements_set to understand replace vs append, or to check if exclusion change explains delivery drop. Also directs users to meta_ads_analysis_placements when they need actual delivery information.

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