products

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

No annotations are provided, so the description carries the full burden. It discloses MODE (mixed), AUTH (OAuth 2.0 required), CREDITS (reads 0, writes 0.5 credits), OUTPUT (Product objects with fields), and details each sub-operation's nature (read/write/destructive). The archive action is explicitly described as destructive.

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 well-structured with headers (MODE, AUTH, CREDITS, OUTPUT, WHEN TO USE) and bullet points for actions. It is moderately sized and front-loaded with purpose. Every sentence adds value, though slightly verbose due to detailed action list.

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 no output schema, the description explains the return format (Product objects with id, name, etc.). It covers all actions, prerequisites for 'create', and references sibling tools. The tool is fairly complex, but the description fully addresses the gaps left by structured fields.

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 adds significant meaning by detailing each enum action with its requirements and the network_code parameter with an example and how to obtain it. However, the schema already documents thoroughly, so a slight bump to 4.

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 the tool manages GAM Products and Product Packages for programmatic direct deals, specifying the verb 'Manage' and the resource. It distinguishes from sibling tools by mentioning the 'deals' tool for creating deals from products.

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 provides an explicit 'WHEN TO USE' section, stating this tool is for managing the product catalogue for Programmatic Direct deals, and refers to the 'deals' tool for creating deals from products, giving clear context and exclusion.

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