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

Annotations already declare readOnlyHint, openWorldHint=false, and destructiveHint=false, covering the safety profile. The description adds a useful default behavior ('Defaults to latest snapshot'), which is not in the annotations. However, it does not disclose pagination behavior, rate limits, or authentication needs beyond what annotations and schema imply.

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 three short, front-loaded sentences. It leads with what the tool does and then adds a use case and a default behavior. Every sentence earns its place with no wasted words.

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 the rich input schema (100% coverage, 8 optional parameters), annotations covering the safety profile, and the presence of an output schema, the description is nearly complete. It covers purpose, a specific use case, and the default snapshot behavior. It does not mention pagination or filtering options, but those are adequately documented in the schema.

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%, so all parameters are fully documented in the input schema. The description mentions 'SKU' and 'quantity per shipment,' but these refer to output fields rather than adding meaning to the parameters. Baseline score of 3 is appropriate when the schema does the heavy lifting.

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 a specific verb ('Get') and resource ('per-SKU line items from AWD shipments') and clarifies the output fields (SKU, quantity per shipment). It implicitly distinguishes from the sibling get_awd_shipments by focusing on line items rather than shipment-level data. However, no sibling is named explicitly.

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 a clear use case: 'Use to prorate AWD/AGL freight charges to specific ASINs.' This gives context for when to invoke the tool. It does not mention when not to use it or name alternative tools, but the intended scenario is explicit.

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