archive_sb_ad_groups

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

No annotations are provided, so the description must fully disclose behavior. It mentions 'guarded write' and preview/archive but does not elaborate on what archiving entails (e.g., deactivation, irreversibility) or side effects. The 'introspection stub' note indicates limited functionality, but key behavioral traits are missing.

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 short (two sentences) and front-loaded with the key action. It is concise without unnecessary detail, though it could be better structured with separate sections for purpose and limitations.

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 tool is a write operation with 5 parameters and no required ones, the description lacks details on return values (no output schema), the difference between preview and archive, and prerequisites. The complexity is moderate but the description is too minimal to fully inform an AI agent.

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 100%, so baseline is 3. The description does not add any parameter-specific context beyond what is in the schema. The 'changes' parameter remains vague ('High-level desired changes') without further clarification.

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?

Description clearly states the action ('Preview or archive') and resource ('Sponsored Brands ad groups'). It is specific and distinguishes from sibling tools like archive_sb_ads (ads vs ad groups) and archive_sb_campaigns, though not explicitly.

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 for hosted endpoints only and that this local server is an introspection stub, providing deployment context. However, no guidance is given on when to use this tool vs alternatives like update_sb_ad_group_state for state changes.

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