Assets Add Callouts

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

The description accurately describes a mutating create-and-attach operation, consistent with readOnlyHint=false and destructiveHint=false. However, it does not add behavioral context such as duplicate handling, partial-failure behavior, or the validate_only dry-run skipping the linking step; those details are left to the schema and annotations.

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?

A single front-loaded sentence with concrete examples and no filler. It economically states both the creation and the attachment behavior.

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?

The tool has full parameter coverage, an output schema, and annotations covering the safety profile, so the call itself is fully actionable. The main gap is lack of routing guidance against the similar assets_add_sitelinks tool, but that does not prevent correct invocation.

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%, including constraints for callouts (2-20 phrases, max 25 characters, no trailing punctuation) and the validate_only dry-run behavior. The description's examples illustrate the callouts parameter but add no semantic information beyond what the schema already provides, so the baseline of 3 is appropriate.

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?

States a specific verb (Creates), resource (callout assets), and target (campaign). It is clearly distinguishable from the sibling assets_add_sitelinks tool because it names callouts specifically, not generic assets.

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?

Provides no explicit when-to-use or when-not-to-use guidance, and does not mention the similar assets_add_sitelinks tool. The intended usage is implied by the action and quoted callout examples, but an agent is not told how to choose between callout assets and other asset types.

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