list_product_source_targets

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

With no annotations provided, the description carries the full burden. It correctly implies a read-only listing operation and specifies the publisher scoping, but it does not disclose pagination behavior, and the word 'all' may overstate results given the limit/offset parameters. It omits details like whether archived targets are included or any permissions/rate limits.

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, front-loaded sentence with no filler. Every word contributes to understanding the tool's core purpose, making it highly concise and scannable.

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?

The tool is relatively simple, and the schema covers parameters, but there is no output schema and no description of the return format or pagination behavior. The phrase 'list all' could mislead an agent into expecting a single complete response rather than a paginated list, leaving notable gaps for a robust tool 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 description coverage is 100%, so parameters are already well-documented. The description adds only minimal context by highlighting 'for a publisher' as the key filter, but it does not provide extra meaning about limit or offset semantics beyond what the schema already states.

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 uses a specific verb ('List'), a distinct resource ('product source targets'), and a clear scope ('for a publisher'). It distinguishes itself from sibling tools like list_product_sources (different resource) and get_product_source_target (singular retrieval), making the purpose unambiguous.

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 when to use the tool (when you need all product source targets for a publisher) but does not explicitly state when to use it over alternatives such as list_product_sources or get_product_source_target, nor does it mention any exclusions or edge cases.

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