get_shipping_rates

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

No annotations are provided, so the description bears the full burden. It states the output (all options with cheapest/fastest markers) but does not disclose side effects, authentication needs, rate limits, or error handling behaviors. It is adequate for a read-only query but could be more transparent.

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 concise: two sentences covering purpose, required inputs, and output nature. Every sentence adds value, no redundancy, and the key information is front-loaded.

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's simplicity as a read query with clear input groups, the description adequately covers its functionality. It mentions the output structure (options with cheapest/fastest markers). However, it could mention potential constraints like carrier availability or date limitations to be fully complete.

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%, so the baseline is 3. The description mentions the four parameter groups but adds no semantic detail beyond what the schema already provides. It does not clarify the relationship between parameters or provide format examples 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 clearly states the tool's purpose: fetching multi-carrier shipping rate quotes and comparison. It specifies required inputs and output nature, but does not explicitly differentiate from sibling tools, though no sibling offers the same functionality.

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 lists required inputs (from_address, to_address, package, ship_date), providing basic usage guidance. However, it lacks explicit when-to-use or when-not-to-use advice, nor does it mention prerequisites or alternatives.

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