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

Annotations already establish read-only, non-destructive behavior, and the description adds useful output transparency: currency, SKU, and quantity-break price structure. It does not mention pagination, auth requirements, or error behavior, but for a read-only GET query the added detail is substantial.

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 front-loaded with what is returned and stays compact, with no filler sentences. It is slightly dense and run-on, but every clause carries useful information about output shape, limits, optional filtering, or endpoint.

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?

With no output schema, the description appropriately explains the return shape and the quantity-break map. It also covers the optional price-list filter and limit, but does not address pagination or default behavior when price_list_ids is omitted beyond implication.

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 the schema already documents both parameters. The description adds meaning by identifying brightpearl_list_price_lists as the source for price_list_ids and clarifying that omitting price_list_ids retrieves prices across price lists, though it repeats the 50-product limit already in the schema.

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 states a specific retrieval operation: product prices per product and price list, including returned fields such as currency, SKU, and quantity-break price map. It also distinguishes the tool from brightpearl_list_price_lists by explaining that price list IDs come from that sibling tool.

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?

It clearly explains that product_ids are required and limited to 50, while price_list_ids are optional and sourced from brightpearl_list_price_lists. It gives usage constraints but does not explicitly compare against siblings like get_products or get_product_availability, so it falls short of full when/when-not guidance.

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