delete_ad

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

No annotations are provided, so the description carries the full burden. 'Archive' does disclose a meaningful behavioral trait - the operation is non-destructive/reversible rather than a permanent deletion - which is valuable given the misleading tool name. However, nothing is said about permissions, side effects on creatives or insights, or whether the ad stops delivering.

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 words, front-loaded and free of padding, but the terseness crosses into under-specification for a mutation tool - no usage context or behavioral caveat is included. It is efficient without being informative enough.

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?

The tool is low complexity (one obvious parameter) and an output schema exists, so return values need not be described. Still, for a mutation with zero annotation coverage, the description should at least indicate the reversibility implications or any preconditions; it states only 'archive' and stops.

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%, but there is only one parameter, ad_id, which is required and self-explanatory from its name. The description adds no meaning beyond the schema, so it neither compensates for the coverage gap nor misleads; a middle score is appropriate.

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?

'Archive ad.' names a specific verb and resource, and crucially clarifies that the operation is an archive rather than the hard delete implied by the tool name delete_ad. It does not, however, differentiate itself from siblings such as delete_adset, update_ad, or delete_campaign, so an agent must infer the boundary itself.

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?

No when-to-use guidance, no prerequisites (e.g., whether the ad must be paused first), and no mention of alternatives like update_ad or delete_adset. The agent gets no routing help at all.

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