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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuine behavioral detail — that access is gated by a private quote access token — but says nothing about failure modes, token scope, or what is returned.

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?

A single tight sentence front-loaded with the verb and resource. Efficient, though minimal enough that it under-delivers rather than being overly dense.

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 a simple two-required-param read tool with annotations covering the safety profile and no output schema, this is borderline adequate. The lack of any parameter format detail and no error/not-found behavior leaves meaningful gaps at 0% schema coverage.

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 0% and neither parameter has a description, so the description carries the full burden. It clarifies that quoteAccessToken is a private access token, which helps for one parameter, but 'id' is left completely unexplained (quote ID? format? source?).

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 (Retrieve) and resource (a saved quote), making it immediately distinguishable from create_quote and the other siblings. It does not explicitly name a sibling or contrast scope, but the read intent is unambiguous.

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?

There is no when-to-use guidance, no prerequisite framing beyond the mention of a token, and no indication of when another tool should be preferred. The agent must infer usage entirely from the name and operation type.

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