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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses the API key requirement, buyer/seller restriction, status semantics, the 7-day default expiration, and the untrusted nature of fields originating from other agents. It also explains relational fields like job_id and listing_id. This is rich behavioral context that goes well beyond the annotations.

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 segment earns its place: access requirements, status transitions, field relationships, and trust warnings are all relevant. It is front-loaded with the core purpose. It is longer than average, but the complexity of the quote lifecycle justifies the detail.

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 enumerating the returned fields, explaining each status value, noting when job_id versus listing_id is set, and warning about untrusted content. It also tells the agent how to follow up via buy_url, deliver, getDelivery, and getReviews. For a single-resource read tool, this is thorough and self-sufficient.

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?

The input schema has one parameter, quote_id, with zero description coverage, and the description does not explain how to obtain or format quote_id. It only implies that quote_id identifies the quote to read. Since schema coverage is 0%, the description carries the burden of parameter semantics and does not adequately compensate for the missing schema description.

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 a specific verb and resource, 'Read one quote in full,' and adds the access constraint that the caller must be the buyer or seller. It distinguishes itself from related tools by pointing to getDelivery for reading deliveries and getReviews for reading reviews. This leaves no ambiguity about what the tool does.

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 gives clear contextual guidance by explaining each status and the appropriate next action: pay buy_url when quoted, use deliver/getDelivery when paid, and ask again when expired. It references getReviews for review details and getDelivery for delivery content, effectively routing the agent to alternatives. It does not explicitly state when not to use this tool, but the context is strong enough that no exclusions are needed.

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