List Sponsored Brands ad groups

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

Annotations already provide readOnlyHint (true) and openWorldHint (true), indicating a safe, non-exhaustive read operation. The description adds the optional filter for campaign ids but does not elaborate on pagination behavior or result structure. With annotations present, the description provides adequate but minimal additional behavioral context.

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, concise sentence that includes the core purpose, API version, and key capability, with no redundant or irrelevant information.

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 list operation with no required parameters and an output schema absent, the description is minimal but sufficient. It leverages the schema for parameter details and annotations for behavioral traits. The lack of output description is acceptable given the tool's simplicity and the presence of pagination parameters in the schema.

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 80%, with four of five parameters documented. The only undocumented parameter (campaignIds) is clarified in the description ('optionally filtered by campaign ids'), adding meaning beyond the schema. The remaining parameters are already well-described in the schema.

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 verb 'List', the resource 'Sponsored Brands ad groups', specifies API version '(v4)', and notes the optional filter 'by campaign ids'. This effectively distinguishes it from siblings like sb_list_campaigns (lists campaigns) and sd_list_ad_groups (ad group list for Sponsored Display).

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 title and description specify 'Sponsored Brands', providing clear context for when to use this tool versus siblings for other advertising product types. While it does not explicitly list alternatives or exclusions, the naming convention and tool hierarchy make the intended use obvious.

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