google_ads_sitelinks_create

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

With no annotations, the description fully discloses critical behaviors: it is mutating, reversible only by google_ads_sitelinks_remove using the returned asset_id, enforces a hardcoded limit of 20 sitelinks per campaign, returns a specific error format, and creates duplicate assets on repeated identical calls. This goes beyond the minimum.

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 concise, with two sentences covering purpose, process, return values, error conditions, limit, reversibility, and duplication. It is front-loaded with the main action and has no redundant wording.

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 mutation tool with no output schema, the description is remarkably complete: it explains the two-step service flow, success and error return shapes, the per-campaign limit, how to reverse the operation, and the duplicate-asset risk. Combined with rich schema descriptions, the context is fully covered.

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 the schema fully documents all parameters. The description adds no extra parameter-level details beyond what's in the schema, which is acceptable given the baseline of 3.

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: 'Create a sitelink Asset and link it to a Google Ads campaign' with a specific verb and resource. It distinguishes from sibling tools like google_ads_sitelinks_list and google_ads_sitelinks_remove by describing the creation flow and the two-step mutate process.

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 implies usage for creating sitelinks but does not explicitly state when to use it versus alternatives like callouts_create. It does mention google_ads_sitelinks_remove for reversal, which is a relevant alternative, but lacks explicit when-not-to-use guidance.

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