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

Beyond the annotations (destructiveHint=true, idempotentHint=true, readOnlyHint=false), the description adds substantial behavioral context: execution is synchronous, task support is forbidden, mutation modes are validate_only/preview_only/execute, and partial failures are not rolled back. It also explains idempotencyKey fallback behavior, the seatId/seatName requirement for multi-seat mutations, and how the returned JSON should be presented to users. No contradiction with annotations.

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 a single dense paragraph with useful information, but it is not concise. The first sentence 'archive campaign' is redundant with the title, and many sentences contain generic instructions about response formatting (e.g., 'Use assistantSummary first,' 'Never display raw JSON') that are not specific to this tool. It is structured as a sequence of metadata declarations rather than a clear, scannable explanation.

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 description covers many operational aspects: execution mode, mutation modes, partial failure, idempotency, seat rules, and response handling. However, it does not clarify the business effect of archiving (what happens to the campaign), whether the action is reversible, or how the optional parameters apply to this tool. The presence of an output schema reduces the need to document return values, but the core purpose and parameter applicability remain incomplete.

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?

With 0% schema description coverage, the description carries the burden of explaining parameters. It does add semantics for idempotencyKey (deterministic retry key) and seatId/seatName (must be supplied on the call when multiple seats are authorized). However, it leaves the other 10 parameters unexplained, including dryRun and several optional IDs (flightId, creativeId, resourceId, etc.) whose relevance to archiving a campaign is unclear. The four mutation modes are not mapped to the dryRun parameter.

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 begins with 'archive campaign,' which simply restates the tool's name and title. It does not explain what archiving entails (e.g., moving to an inactive state, hiding from active lists, or unavailability for further edits) and does not distinguish this from sibling tools like archive_advertiser or archive_creative beyond the resource name. The verb 'archive' is specific, but the intended business effect is absent.

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 provides no guidance on when to use this tool versus alternatives. It does not mention scenarios where archiving is appropriate, nor does it exclude cases where other actions (e.g., delete_flight, update_campaign, cancel_task) would be preferable. The metadata about mutation modes and partial failure is useful but does not address selection criteria.

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