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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered; the description adds genuinely new behavioral context by disclosing the 5-minute ordering window tied to expiresAt. It still doesn't say what happens when the quotation has expired (error vs. stale data), which is the main behavioral unknown for a read-only fetch.

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?

One compact sentence with the resource front-loaded and no filler; the enumeration of return fields earns its place because no output schema exists. The telegraphic fragment style ('A quotation by id: ...') costs it a point on readability.

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 usefully enumerates the return payload and the expiry constraint, which is what an agent needs to decide whether to use or re-create a quotation. The remaining gap is error/expiry behavior, minor for a single-parameter read tool whose annotations cover safety.

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% and the single parameter already documents the id format and where it comes from (quotationId from lalamove_create_quotation), so the description adds nothing about the parameter. Baseline 3 is appropriate when the schema carries the full burden.

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 identifies the specific resource (a quotation by id) and the endpoint GET /v3/quotations/{quotationId}, and enumerates what the response contains (stops with stopId, vehicle, price breakdown, currency, distance, expiresAt), which clearly separates it from the mutating siblings like lalamove_create_quotation or lalamove_place_order. It lacks an explicit verb ('Retrieve'/'Fetch') so the phrasing is a fragment rather than a full statement of action.

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 is only implied: the note that 'a quotation can be ordered for 5 minutes' hints that this should be called shortly before ordering, and the sibling list makes the create-vs-get split inferable. There is no explicit when-to-use/when-not statement, no mention of calling this after lalamove_create_quotation or before lalamove_place_order, and no guidance for expired quotations.

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