Create ad unit mapping

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

Annotations already mark this as non-readOnly and destructive. The description adds that a dryRun parameter can be used to validate without executing, and that the operation runs after confirmation from the client. This goes beyond 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?

Two concise sentences: first states purpose and constraints, second explains key parameter relationships. No filler, front-loaded.

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 complexity (6 params, nested object, no output schema), the description covers the creation process, parameter dependencies, and the dryRun behavior. Missing output details but acceptable without output 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?

With 67% schema coverage, the description adds significant meaning for adapterId and adUnitConfigurations by specifying their sources. DryRun and publisherId are already covered in schema. AdUnitId and displayName lack extra info, but overall adds value.

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 tool creates an ad unit mapping connecting one ad unit to a mediation adapter, specifying the version and allowlist restriction. It distinguishes from sibling tools like the batch variant.

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 guidance on where to obtain adapterId (from admob_list_adapters) and that adUnitConfigurations keys come from adapterConfigMetadataId. Lacks explicit when-to-use vs. alternatives but the context is clear.

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