firestarter_shipping_options

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful context: it returns a numbered menu, is a preview before paying, and clarifies that actual ordering happens via firestarter_approve. It also explains refresh and select_index behaviors, though it doesn't cover failure modes or edge cases.

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 dense but every sentence contributes: purpose, return format, next-step action, when-to-use, parameter guidance, and alternative tool. Front-loaded with the core function and efficiently 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?

Despite no output schema, the description fully covers return contents, workflow, parameter behaviors, and alternative tools. It provides enough context for an agent to decide when and how to invoke the tool, and what to do with the result.

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 covers 100% of parameters with descriptions, so baseline is 3. The description adds extra value by explaining how select_index maps to the shipping_option_index used with firestarter_approve, and how refresh re-fetches stale rates. This goes beyond schema descriptions.

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 explicitly states the tool's function: to show and compare delivery speeds for an order awaiting approval, and preview re-priced totals before payment. It distinguishes itself from sibling tools by noting that firestarter_execute lists options inline and firestarter_shipping_estimate is for pre-execution listings.

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?

Provides clear when-to-use scenarios (buyer asks about delivery speed/cost, wants faster, or wants trade-off before approval) and explicitly calls out when not to use it (if firestarter_execute already lists them inline, or use firestarter_shipping_estimate for pre-purchase listings). This is ideal guidance.

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