store_list_shipping_carriers

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds no behavioral context such as response format, pagination, filtering capabilities, or any side effects, which are absent from the description.

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 extremely brief with no fluff, which is concise, but it omits necessary details. It is under-specified rather than thoughtfully concise, so a middle score is appropriate given the trade-off between brevity and informativeness.

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 tool has no output schema, so the description should explain what is returned or any relevant behavioral aspects. It does not mention pagination, sorting, the structure of the list, or how altType affects results. This is a significant gap for a list operation, leaving the agent uncertain about the outcome.

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 documents both parameters (altId and altType) with descriptions, achieving 100% coverage, so the description does not need to repeat them. However, the description also doesn't clarify how these optional parameters affect the list response, which would be useful for understanding their role beyond the schema.

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 states the verb 'List' and the resource 'Shipping Carriers', making the core purpose clear. However, it does not differentiate from the sibling tool store_get_shipping_carriers, which could perform a similar function, so it lacks the specificity to distinguish among similar tools.

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 provides no guidance on when to use this tool versus alternatives like store_get_shipping_carriers or store_list_shipping_rates. No context, exclusions, or comparisons are given, leaving the agent to infer usage from the name alone.

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