Archive ad groups

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

Beyond the destructiveHint/idempotentHint annotations, it discloses the consequences that actually drive a decision: archived groups stop serving and Pinterest cannot un-archive them. The required confirm='ARCHIVE' gate is a concrete behavioral requirement the annotations do not convey.

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 tight sentences with the action and irreversibility front-loaded before the alternative. No redundant restatement of the title, though the confirm clause is slightly compressed into the consequence sentence.

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?

Output schema exists so return values need not be described, and annotations cover the safety profile; the description supplies irreversibility, the confirm gate, and the pause alternative. The remaining gap is scope-related: whether ad_account_id is required context and how partial failures across multiple ids behave.

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 0%, so the description must carry parameter meaning. It does well for 'confirm' by specifying the exact literal 'ARCHIVE', but says nothing about 'ad_account_id' or the id-array format, leaving one of three parameters undocumented everywhere.

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 and resource ('Archive ad groups by ID') that an agent can immediately distinguish from siblings like pinterest_ads_archive_campaigns, pinterest_ads_archive_ads, and pinterest_ads_update_ad_groups.

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 routes the agent: use this to permanently archive, but use pinterest_ads_set_statuses with PAUSED for a temporary stop. It also states the precondition that the user must agree before calling, leaving nothing to inference.

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