ghl_store_list_shipping_carriers

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds only endpoint details, which are redundant. No additional behavioral traits (e.g., pagination, rate limits, error conditions) are disclosed.

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 short but includes a repetitive phrase ('List Shipping Carrier' vs title) and unnecessary endpoint technical details. Could be more concise and focused.

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 description lacks information about the return value structure, scoping to location, and any limitations. For a simple list tool, it should at least state what fields are returned or that it requires valid altId/altType.

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?

The schema has 50% coverage (altId described, altType only enum). The description does not explain any parameters, missing an opportunity to clarify altType's purpose or the role of the two 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 clearly states 'retrieve a list of shipping carrier', which aligns with the tool name and distinguishes it from sibling tools like get/create/delete/update. However, it could be more precise by specifying that it lists carriers for a given location.

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 such as ghl_store_get_shipping_carrier or ghl_store_list_shipping_rates. The description does not mention prerequisites or context.

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