Get promotional products

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that the tool returns only promotional products and can be filtered by retailer, which is a modest behavioral clarification, but it does not explain pagination behavior or the returned data structure beyond the implied list of products.

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 redundant words. It conveys the essential purpose and the main optional parameter without unnecessary elaboration.

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 annotations cover safety and idempotency. However, with no output schema and a minimal description, the agent is not informed about pagination, return format, or how results are ordered. The schema provides defaults and limits for page/page_size, but the description does not tie these together into a complete operational picture.

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 only 33% (only 'page' has a schema description). The tool description clarifies the 'retailer' parameter by stating it is an optional filter, but it does not explain 'page' or 'page_size' semantics beyond what the schema provides, leaving the agent without additional guidance for pagination.

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 the verb 'Get' with the resource 'promotional products' and adds an optional retailer filter, clearly indicating what the tool does. The qualifier 'promotional' distinguishes it from general product listing tools like list_products, though it does not explicitly reference sibling 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?

The description gives no guidance on when to use this tool versus alternatives such as list_products or get_products_by_retailer. It mentions an optional retailer filter, but does not state any exclusions, prerequisites, or scenarios where this tool is preferred.

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