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

No annotations are provided, so the description carries the full burden. It does disclose that this is a read operation ('same data as GET') and surfaces the meaningful output semantic that the product code feeds ProductCode at label creation, but it omits response shape, filtering behavior, and error/empty-result handling.

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?

Two tightly packed sentences with the core purpose front-loaded and no wasted words; the parenthetical endpoint reference and the ProductCode linkage both earn their place.

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?

There is no output schema and no annotations, so the description should explain the return values more. It does provide the single most important output semantic (ProductCode for label creation), but for a 9-parameter listing tool it leaves the rest of the response structure and behavior unstated.

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% and each of the 9 parameters is self-documenting in the schema. The description adds the label-creation meaning of the resulting product code but nothing about the input parameters, so baseline 3 applies.

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+resource ('Shipping methods available for a route') and pins the purpose by equating it to GET /api/Shippingmethods. Clear what it returns, but it doesn't differentiate itself from the similar sibling get_carrier_routes.

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?

Usage is only implied through the note that the product code is used as ProductCode when creating a label, which hints at the create-label workflow, but it never states when to prefer this over alternatives like get_carrier_routes or SearchParcelShops.

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