List Sponsored Products product ads

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds that it lists 'which ASINs/SKUs are advertised in which ad groups, with states,' which provides relationship context. However, it does not disclose pagination behavior, default parameter values, or ordering, so it adds limited value 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?

The description is a single, information-dense sentence that captures the core functionality without fluff. It is front-loaded with the key verb and resource, making it efficient for scanning.

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 there is no output schema, the description should compensate by explaining what the response contains (e.g., fields of each product ad). It does not. While annotations cover safety and scope, the description omits output structure and critical details like result ordering or token usage, leaving the agent underinformed.

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?

All 6 parameters have descriptions in the input schema (100% coverage), so the schema already explains each parameter fully. The description adds no additional parameter information beyond the schema, earning the baseline score of 3.

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 'List Sponsored Products product ads (v3): which ASINs/SKUs are advertised in which ad groups, with states.' This provides a specific verb ('List'), resource ('product ads'), and scope ('Sponsored Products'), and distinguishes from sibling tools like sp_list_ad_groups or sp_list_campaigns.

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 lacks any guidance on when to use this tool versus alternatives (e.g., sp_list_ad_groups, sp_list_campaigns). No exclusions or context for selection are provided, leaving the agent to infer usage solely from the name and sibling list.

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