ghl_product_price_list

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds value by disclosing OAuth scopes (products/prices.readonly), pagination behavior via limit/offset, and filter capability via the 'ids' parameter. This goes beyond structured fields.

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 concise with four sentences covering purpose, endpoint, scopes, and pagination. Information is front-loaded and efficient, though the technical details (endpoint, headers) could be more integrated.

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 has 5 parameters, 2 required, and no output schema. The description covers purpose, endpoint, auth scopes, and pagination, but does not describe the return format or data structure, which is a gap given the lack of output schema.

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?

With 100% schema coverage, the baseline is 3. The description mentions 'filtering prices' (referring to ids) and pagination, but does not add meaningful detail beyond what the schema already provides (e.g., `example` and `description` fields).

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 'List Prices for a Product' and explains the tool retrieves a paginated list of prices for a specific product. The verb 'List' and resource 'prices' are specific and unambiguous, though it does not explicitly differentiate from sibling tools like ghl_product_price_get.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., ghl_product_price_get for a single price). The description focuses on technical details like endpoint and OAuth scopes but omits contextual usage advice.

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