get_custom_audience

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

No annotations are provided, so the description carries the behavioral disclosure burden. It adds useful context that the response exposes processing state and membership_revision and positions the call as a precondition for mutations, but it does not state read-only/no-side-effect behavior, required permissions, or output/error behavior.

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 short sentences, with the core action front-loaded and the warning in the second. No filler or repeated schema content.

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?

As a simple read-by-ID tool, the description provides the essential required parameter and a valuable precondition hint. However, with no output schema and no annotations, it omits return value details and leaves the two optional parameters unexplained, so it is not fully complete.

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 only 33% and the description only paraphrases custom_audience_id via 'by ID'. ad_account_id and matched_count_granularity receive no explanation, so the low schema coverage is not compensated.

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?

States a specific verb ('Get'), target resource ('custom audience'), and lookup method ('by ID'), which clearly separates it from list_custom_audiences and mutation siblings. The additional mutation-check guidance reinforces its role as a read tool.

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?

The second sentence tells the agent to use this tool to check processing state and membership_revision before mutations, giving a clear use context. It does not explicitly name alternatives or exclusion cases, but the context is enough for distinguishing from sibling list/create tools.

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