list_shipping_classes

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

Annotations already declare readOnlyHint=true, so the safe-read behavior is known. The description adds context about the purpose of shipping classes but does not disclose any additional behavioral traits such as pagination behavior, sorting, or what fields are returned by default. It does not contradict annotations, and the added conceptual information provides some value beyond the 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 two short sentences, front-loaded with the core action and resource. The second sentence adds useful conceptual context without redundancy. Every word earns its place, making it highly concise and well-structured.

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 simple read-only list tool with good annotations and complete parameter schema, the description sufficiently explains what the tool does and the concept of shipping classes. It does not explain return value details, but the absence of an output schema and the low complexity make additional explanation unnecessary. A slightly higher score would require more behavioral details like pagination or filtering nuances.

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 100%: all three parameters (page, fields, per_page) have descriptions in the input schema. The description adds no additional parameter information beyond what the schema already provides, so it meets the baseline of 3 for high schema coverage.

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 begins with 'List product shipping classes', a specific verb+resource pair that clearly states the tool's function. It distinguishes itself from sibling tools like list_shipping_zones by naming the resource explicitly and adds conceptual context (grouping products with similar shipping requirements).

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 for listing shipping classes and explains what they are, but it does not explicitly state when to use this tool versus alternatives such as list_shipping_zones or create_shipping_class. No exclusions or alternative references are provided, making the guidance implicit rather than explicit.

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