archive_custom_audience

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does state the main consequence—archived audiences cannot be used for targeting—but it does not disclose reversibility, impact on existing campaigns or ads that reference the audience, or what happens to the audience data itself. This is meaningful but incomplete.

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 no filler; the action is front-loaded and the consequence in the second sentence earns its place. The structure is compact and immediately scannable.

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 archive action, the description covers the core purpose and effect, which is largely adequate. However, without annotations or an output schema, it leaves gaps around reversibility, return value or operation status, and the optional ad_account_id parameter, 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?

The description adds no parameter-level meaning; it only refers to 'a custom audience' generally. The schema describes custom_audience_id, but ad_account_id has no description, and with schema description coverage at 50% the tool description needed to compensate for the undocumented ad_account_id but does not.

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 precise verb ('Archive'), a specific resource ('custom audience'), and a concrete consequence ('Archived audiences cannot be used for targeting'). This clearly differentiates it from sibling audience tools like list_custom_audiences, merge_custom_audiences, and add_audience_members, as well as archive variants on other entities.

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 consequence 'Archived audiences cannot be used for targeting' implies the tool is for making an audience unavailable for targeting, but there is no explicit guidance on when to choose this over alternatives such as remove_audience_members or whether archiving is reversible. Usage context is therefore implied rather than explicitly instructed.

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