ghl_store_list_shipping_rates

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

Annotations already provide readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds pagination behavior and endpoint details, but does not cover potential issues like rate limits, default page size, or data filtering. It adds some value beyond annotations but not extensive.

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 three sentences plus a title. It is mostly concise, though the endpoint details are technical but not overly verbose. Could be slightly tighter but still efficient.

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 5 parameters, 3 required, 80% schema coverage, and no output schema, the description covers the main purpose and pagination. However, it does not explain the expected return structure or data fields, which would be helpful for an agent without an 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?

Schema description coverage is 80%, so most parameters are already documented. The description adds context for pagination parameters ('pass them to page through full result sets'), but does not elaborate on altId, altType, or shippingZoneId beyond what schema provides.

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 the tool lists shipping rates for a specific shipping zone, with verb 'retrieve a list of shipping rate'. It distinguishes from sibling tools like 'get_shipping_rate' (single) and 'get_available_shipping_rates' (different function).

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 mentions pagination usage but does not provide explicit guidance on when to use this tool versus alternatives like ghl_store_get_shipping_rate or ghl_store_get_available_shipping_rates. Usage context is implied but not directly stated.

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