List products

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

The annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful behavioral detail beyond that: location scoping, pagination support, optional search, and the downstream value of returned IDs. There is no contradiction with the 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 two sentences with no filler. It front-loads the core action and scope, then adds the most important downstream guidance about product IDs. Every sentence earns its place.

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?

For a read-only list operation with four optional parameters, the description covers location, pagination, search, and the purpose of the results. There is no output schema, so a bit more detail about the response shape could help, but the mention of product IDs plus the read-only annotations makes the tool usable without major gaps.

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 50%, with search and locationId documented there; limit and offset have no descriptions but their names and defaults make their purpose clear. The description mentions pagination and optional search but does not add meaning beyond what the schema already provides. This is adequate but not a strong compensatory explanation.

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-resource pair ('List products') and adds location scoping plus pagination and search. It also clearly connects the tool to downstream use cases (adding prices, building invoices/estimates), which distinguishes it from other product-related tools like get_product or list_product_prices.

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 clear context on when to use the tool and what to do with its results: retrieve product IDs for prices, invoices, and estimates. It does not explicitly exclude alternatives or state when not to use it, but the use case is concrete enough for an agent to select it appropriately.

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