archive_sd_targets

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

With no annotations, the description carries the burden. It reveals guarded write behavior via '[Ads / guarded write]' and the stub nature locally. However, it does not disclose side effects (e.g., what archiving does to targets), permissions needed, or whether operations are reversible.

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?

The description is extremely concise with two substantive sentences, each adding unique value: purpose and environment. No wasted words.

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?

Given the lack of output schema and annotations, the description adequately identifies the tool as a stub with guarded write capability. However, it does not explain return values, error states, or when to use preview vs. archive, leaving gaps for an agent to interpret.

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 100%, so parameters are already described. The description adds context connecting 'preview' and 'dry_run' to the overall behavior, but does not provide additional meaning beyond the schema descriptions.

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?

The description clearly states the tool can preview or archive Sponsored Display targets, with a verb and specific resource. It also distinguishes itself from sibling archive tools by specifying the resource type. However, it doesn't explicitly define what 'archive' means in this context.

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 description notes that the tool is a local introspection stub and hosted endpoint only, which sets expectations. But it provides no guidance on when to use this tool vs. sibling archive tools (e.g., archive_sd_ad_groups) or when to prefer preview over archive.

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