archive_advertiser

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

With no annotations provided, the description carries full burden. It discloses the soft-delete and restore behavior, but does not mention side effects on related entities, permissions required, or the resulting listing in archived endpoints. This is basic but lacks depth.

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?

Single sentence, front-loaded with the action, and includes the most important qualifier. 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?

For a simple one-parameter tool, the description is sufficient. It does not need to explain return values since there is no output schema, but it could have pointed to list_archived_advertisers/unarchive_advertiser for lifecycle context. Still, it is complete enough for correct invocation.

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%: the 'id' parameter is documented as 'Advertiser ID'. The description adds no extra parameter context, but none is necessary—the schema fully defines the single 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 states the action precisely: 'Archive an advertiser' with the clarifying note '(soft-delete, can be restored later)'. This distinguishes it from the sibling delete_advertiser and aligns with unarchive/archive list tools.

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 phrase 'soft-delete, can be restored later' clearly implies the use case of temporarily disabling an advertiser versus a hard delete. While it does not explicitly name alternatives, the context guides the agent to reserve archive for reversible actions.

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