firestarter_assist_quote

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

The description adds key behavioral context beyond annotations: it does not book or charge, returns quotes sorted cheapest-first with a quote_ref, requires human price confirmation before booking, and notes that some couriers like Lalamove Thailand require coordinates. These details meaningfully shape agent behavior. No contradiction with annotations is apparent.

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?

All sentences are dense and purposeful: definition, use cases, cost implication, coordinate exception, and booking next step. The examples 'weight racks, sofas, appliances' aid disambiguation without padding. Well structured and 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?

For an 11-parameter, no-output-schema tool, the description covers purpose, pricing behavior, return ordering, coordinate constraints, and handoff to booking. It could detail the returned quote fields more, but the agent has sufficient context to use quotes and quote_ref correctly.

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 descriptions cover about 55% of parameters; the description compensates by explaining why pickup_lat/lng and dropoff_lat/lng matter (couriers may refuse without coordinates), giving examples for bulky/weight_kg/two_person, and mentioning quote_ref. It does not fully clarify needs_disassembly or coordinate formats, but provides enough for most invocations.

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 opens with 'Get pickup+delivery quotes for a PHYSICAL item, including loading/unloading help', which names the exact action, object, and distinguishing features. It explicitly scopes to bulky/heavy goods and contrasts with booking by directing to firestarter_assist_book, separating it from sibling 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?

Provides explicit 'Use when' conditions (buyer/seller asks how to move an item, or proactively when item is clearly bulky) and tells when not to book by saying 'Pure price check: books nothing, charges nothing.' It also instructs to include lat/lng when a location pin is shared and to confirm price with the human before calling firestarter_assist_book, giving concrete guidance and an alternative.

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