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

readOnlyHint=true already declares this is a safe read, and the description adds nothing behavioral beyond that: no mention of pagination behavior, default page size, result caps, or response shape. The endpoint note 'GET /SalesQuotes/{page}' merely restates the page parameter already documented in the schema.

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 front-loaded sentence with the resource first and its filters second, followed by a short endpoint reference. No padding or redundancy in the prose, though the endpoint fragment is marginal value.

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 8-parameter list tool with a read-only annotation and full schema coverage, the description covers selection well. However, there is no output schema, so nothing anywhere describes the returned quote records or pagination envelope, which is the remaining gap.

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%, so all eight parameters are already documented (including the non-obvious 'quoteNumber overrides other filters'). The description's filter list is broader but less precise than the schema, so it adds no meaning beyond what the schema provides.

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 ('List sales quotes') and enumerates the filter dimensions (status, customer, quote number, date range), so an agent knows exactly what the tool returns. It does not explicitly contrast itself with close siblings like unleashed_list_sales_orders or unleashed_list_invoices, leaving that distinction to the resource name alone.

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 filter list implies the retrieval context (pull quotes narrowed by status/customer/number/date), but there is no explicit when-to-use statement, no prerequisites, and no guidance on choosing this over list_sales_orders. Usage is inferable but not stated.

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