update_sd_product_ad_state

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

Without annotations, the description reveals 'guarded write' behavior and preview capability but omits details on side effects, permissions, or error handling. The stub context reduces expectations, but an agent needs more operational clarity.

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 that efficiently convey purpose, modality (preview/set), hosting context, and stub nature. No unnecessary words.

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 5 optional parameters and no output schema, the description lacks detail on expected return values, outcome of a write, or exact structure of 'changes'. It is adequate for a stub but incomplete for production use.

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 coverage is 100%, but the description adds value by clarifying 'dry_run' as an alias for preview and describing 'changes' as high-level desired changes. This goes beyond the schema's basic descriptions.

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 specifies 'Sponsored Display product ad state' with verb 'Preview or set', distinguishing it from sibling tools like update_sd_ad_state. It identifies as a 'guarded write' and notes it's a hosted endpoint stub.

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?

It indicates two usage modes (preview/set) and states it's a stub for introspection, implying limited functionality. However, it does not explicitly contrast with related siblings or provide criteria for when to use preview vs set.

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