get_product_ads

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the read operation implied by the tool name and does not describe the return format, pagination behavior, or what happens when no filters are provided. This adds minimal value beyond the name.

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 sentence that front-loads the verb and object, with no filler or redundant phrasing. It is appropriately concise for the information it conveys.

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 simple and has only three parameters, so the description is not severely incomplete. However, without an output schema or annotations, the description should have explained response behavior and the optionality of filters to be fully complete.

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 already describes all three parameters with 100% coverage, so the baseline is 3. The description adds no meaningful parameter semantics beyond echoing the campaign/ad group filter concept, which is already in the schema.

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 ('Retrieve') and a clear resource ('product ads'), with scoping to 'a specific campaign or ad group.' This clearly distinguishes it from sibling tools like get_keywords and get_campaigns, which target different resources.

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 the tool is for fetching product ads associated with a campaign or ad group, but it does not explicitly discuss when to prefer this over sibling tools, nor does it clarify that campaignId and adGroupId are optional filters. The phrase 'for a specific campaign or ad group' slightly conflicts with the schema, where both filters are optional.

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