List product prices

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description does not need to restate safety. It adds slight context with 'configured', but gives no detail on pagination, ordering, or response shape. This is acceptable given annotations but not rich.

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 concise sentence with no filler. The verb and object are front-loaded, making it immediately clear what the tool does.

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 low schema coverage and no output schema, the description is too sparse. It does not mention that productId is required, how pagination works, or what the response contains. An agent would have to guess about the return structure and parameter details, so the description is not complete enough for confident invocation.

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 25% (only locationId has a description). The description does not explain productId, limit, or offset, despite productId being required and the other two being pagination controls. The phrase 'for a product' implies productId but does not elaborate on its meaning or the behavior of the other parameters.

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') and a specific resource ('prices configured for a product'), clearly distinguishing this from siblings like ghl_list_products (which lists products) and ghl_create_product_price (which creates a price). The scoping phrase 'for a product' makes the tool's object clear.

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 conveys that this tool lists prices for a given product, giving clear context on when it is appropriate. However, it does not explicitly mention alternatives or when not to use it (e.g., for creating prices one would use ghl_create_product_price).

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