ads_write_many

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description goes beyond them by disclosing that each write is individually gated, audited, and that the batch aborts at the first refusal — meaningful behavioral context for a destructive batch operation.

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 dense sentences with the batching, format, and failure policy all front-loaded. No filler.

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?

With an output schema present, return values needn't be explained, and the description adequately covers format, gating, auditing, and abort semantics for a batch writer. Only the relationship to sibling write tools remains unstated.

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 schema documents a single free-form object at 0% coverage. The description compensates partially by specifying the '{name: value}' shape, but adds no detail on value typing, size limits, or ordering guarantees beyond 'sequentially'.

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+resource ('Write several symbols') and the format ('{name: value}'), which naturally distinguishes it from the singular ads_write and the raw variants. It doesn't explicitly name the sibling it supersedes, but 'several' clearly scopes it.

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 batch write usage and notes fail-fast behavior, but never states when to prefer this over ads_write, ads_write_raw, or ads_read_many, nor any prerequisites. Usage must be inferred from the name.

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