create_sd_product_ads

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

No annotations provided; description only says 'guarded write' and 'introspection stub'. It does not explain behavioral traits like side effects (actual creation vs. preview), required permissions, rate limits, or error handling. The agent lacks critical context for safe invocation.

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 sentences, no wasted words. However, the second sentence about the server being an 'introspection stub' is meta and may distract from the tool's purpose. Still, overall concise and 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 (5 parameters, no output schema, many siblings), the description is severely lacking. It does not explain return values, how to use the 'changes' parameter, or the difference between preview and create. The agent cannot reliably use this tool based solely on the description.

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%, so baseline is 3. The description does not add any parameter-specific guidance beyond what the schema provides. For instance, it does not clarify the relationship between 'preview' and 'dry_run' or the expected format of 'changes'.

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 it can 'Preview or create Sponsored Display product ads', specifying the resource (SD product ads) and the actions. It also labels the tool as 'Ads / guarded write', distinguishing it from sibling tools like archive or update tools.

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?

No explicit guidance on when to use this tool versus siblings (e.g., create_sd_ad_groups, create_sd_campaigns). The description mentions 'Hosted endpoint only' and 'introspection stub', but does not guide the agent on selecting this tool for actual creation vs. preview, or when to use it over archive/update tools.

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