google_ads_sitelinks_list

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It states read-only, merges campaign and account levels, deduplicates by id, and returns a specific structure. While it does not mention rate limits or auth requirements, for a read-only list tool, the behavioral transparency is nearly complete.

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 front-loaded with the core purpose and return format. It efficiently packs usage guidance, behavioral details, and sibling references into a few sentences. Slightly verbose in parts (e.g., 'Read-only' could be integrated), but overall well-structured and each sentence earns its place.

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's simplicity (list with 2 parameters) and no output schema, the description is remarkably complete. It explains the merged output, deduplication, level indicator, usage context, and related tools. It provides everything needed for an agent to select and invoke the tool correctly.

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?

The input schema already provides descriptions for both parameters (customer_id and campaign_id) with high coverage (100%). The description adds further context: customer_id is optional with fallback to environment variables, and campaign_id can be obtained via google_ads_campaigns_list. This adds meaning beyond 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 'List sitelink assets attached to a Google Ads campaign, merging campaign-level and account-level entries.' It specifies the verb (list), resource (sitelink assets), scope (attached to a campaign), and distinguishes from sibling tools like google_ads_callouts_list.

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 explicit guidance on when to use this tool: 'Use this to audit extensions before calling google_ads_sitelinks_create (20 per-campaign limit) or google_ads_sitelinks_remove.' It also mentions an alternative: 'For callouts use google_ads_callouts_list.' This clearly indicates when to use and when not to use this tool.

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