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

Adds genuinely non-obvious behavior beyond annotations: the ~5 minute expiresAt, that nothing is ordered or charged (clarifying the readOnlyHint=false), and the POST /v3/quotations endpoint. It does not discuss rate limits or failure modes, keeping it just short of a 5.

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?

Four tight sentences front-loading the core action, then return values, then the safety disclaimer, then prerequisites. No filler; every sentence carries distinct information.

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?

With no output schema, the description compensates by naming the returned fields (quotationId, stopId, price breakdown, currency, distance, expiresAt). Nested-object complexity and the 8-parameter surface are adequately covered by the schema plus this text.

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 baseline is 3; the description still adds value by clarifying that the first stop is the pickup and the remainder are drop-offs, and by pointing to lalamove_list_cities as the source of service_type values. Most other parameter detail is repeated from 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?

States a specific verb and resource ('Price a delivery') plus scope (2-16 stops, vehicle type, optional extras), and explicitly disambiguates from lalamove_place_order by saying it creates a quotation and nothing is ordered. An agent can immediately tell it apart from get_quotation and place_order.

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?

Names the prerequisite sibling ('Get the vehicle keys from lalamove_list_cities') and prescribes the workflow step ('Show the price to the user before placing an order'). Both the when and the sequencing relative to alternatives are explicit.

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