ghl_store_list_shipping_carriers

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the bar is lower; the description still adds the auth requirement of a location token plus the concrete endpoint and API version, which is real context beyond the annotations. It omits pagination and result-size behavior, keeping it from a 5.

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 core purpose is front-loaded, but three lines are spent on API metadata (endpoint path, version header, JSON source file) that adds little for an agent selecting a tool, and the first two sentences restate the same thing.

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?

For a 2-required-param read tool with no output schema, the description covers auth and the endpoint but says nothing about the returned carrier fields, pagination, or whether results are scoped per location. Adequate but with clear gaps.

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 50%: altId is documented as 'Location Id or Agency Id' but altType (enum 'location') has no schema description. The description's note about a location token loosely maps to altId but adds nothing for altType, so it neither compensates for nor worsens the coverage gap.

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?

States a specific verb and resource ('List Shipping Carriers' / 'retrieve a list of shipping carrier') that clearly separates it from single-record siblings like ghl_store_get_shipping_carrier. The title line and API sentence are redundant but the intent is unambiguous.

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 explicit when-to-use or alternatives are named; selection versus ghl_store_get_shipping_carrier or ghl_store_get_available_shipping_rates is left implicit. It does state a prerequisite ('Requires a Sub-Account (location) token'), which gives partial usable context.

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