ghl_store_get_shipping_zone

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

While annotations declare readOnlyHint, the description adds little beyond the endpoint URL and source. It incorrectly describes the operation as a 'list' with pagination, which contradicts the actual single-resource retrieval, and fails to disclose behavior such as what happens when the zone is not found or authentication requirements.

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 contains redundancy (title repeated) and confusing terminology ('List' instead of 'Get'). It could be clearer and more concise.

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 no output schema, the description should explain what is returned. It does not mention the purpose of altId and altType (location/agency context) or the return format. The pagination mention is irrelevant and misleading. The description is incomplete for a get-by-ID operation.

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 high (75%), so the schema already describes parameters. The description does not add any parameter-specific meaning beyond what is in the schema, so baseline 3 is appropriate.

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 is confusing: it states 'Get Shipping Zone' but then says 'List Shipping Zone' API and mentions 'paginated list', while the input schema requires a single shippingZoneId, indicating a get-by-ID operation. This contradiction makes the purpose unclear and potentially misleading.

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?

There is no guidance on when to use this tool versus alternatives like ghl_store_list_shipping_zones or other CRUD operations. No context is provided about prerequisites or typical scenarios.

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