ghl_store_get_available_shipping_rates

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

Annotations provide readOnlyHint=false and other hints. The description states it returns rates but does not disclose side effects, authentication needs, or rate limits. The POST endpoint could imply mutation, but this is not clarified. The description adds minimal behavioral context beyond 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 somewhat repetitive (three sentences with similar meaning) and includes a technical note about the endpoint and correction. It is not excessively long, but could be more streamlined.

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 no output schema, so the description should explain the return structure. It only says 'returns the shipping rates' without describing the format, fields, or how to interpret the response. Given the complexity of inputs, more guidance is needed.

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 100%, so baseline is 3. The description highlights key inputs (country, order amount) but does not explain the role of other required parameters like altId, products, etc. It adds some value beyond schema but not comprehensive.

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 that the tool returns shipping rates for a given country/order-amount combination. It corrects a previous misnomer (zones vs rates), and the name itself is descriptive. While it distinguishes from 'list' and 'get single rate' siblings, it does not explicitly differentiate from other shipping rate tools.

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 implies usage when needing rates based on country and order amount, but does not provide explicit when-to-use, when-not-to-use, or alternative tools (e.g., list all rates). No exclusion criteria or context for selecting this over siblings.

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