google_ads_sitelinks_list

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

Describes key behaviors: read-only, merges levels, deduplication by id, return format including 'level' field. Despite no annotations, the description is transparent. Minor omission: no mention of error handling or rate limits.

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?

Concise and well-structured: action first, then output format, then usage tips. No redundant sentences; every sentence adds value.

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?

Provides output structure, deduplication logic, and cross-references to sibling tools. However, lacks mention of pagination or limits on number of sitelinks returned.

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%, and the description adds value by explaining customer_id fallback and campaign_id source (google_ads_campaigns_list). This goes beyond the schema's 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 action (list), resource (sitelink assets), and scope (attached to a campaign, merging campaign and account levels). It distinguishes from sibling tools by referencing create/remove and callouts.

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?

Explicit usage guidance: use for auditing before create (with limit note) or remove, and directs users to google_ads_callouts_list for callouts. This covers when and when not to use the tool.

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