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

The description adds behavioral detail beyond annotations—resolves items, computes total weight, quotes couriers—and reinforces the read-only, side-effect-free nature. Annotations already declare readOnly and non-destructive, so the description provides useful but not extensive additional context.

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 sentences, front-loaded with the primary action, and every sentence provides value. The 'Read-only, side-effect-free' phrase is slightly redundant with annotations but reinforces safety without waste.

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 tool is a UI opener with no output schema, the description sufficiently covers the main function and safety profile. It could mention what the widget returns or how it appears, but for this type of tool the detail is adequate.

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 the schema already explains all parameters clearly. The description adds no new parameter-level meaning beyond implying that 'items' are resolved against catalog data, which is marginal.

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 clearly states the tool combines catalog stock/weight data with a live shipping quote into a single widget, with specific actions like resolving items and computing total weight. It distinguishes from quote_shipping by emphasizing the combined nature, though it doesn't explicitly name alternatives.

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 context is implied: use when you need a consolidated shipment prep view with weight and quote. However, no explicit when-to-use vs alternatives (e.g., quote_shipping for quote-only) is provided, and exclusions are not stated.

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