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 real context beyond them: it discloses that results are paged, and that the record shape mirrors invoices — valuable given there is no output schema. It does not disclose default/max page size or whether a total count 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?

Two brief sentences, front-loaded with the resource and scope. The trailing 'SOAP GetQuotes' is implementation noise that adds little for an agent selecting the tool, but the overall size is well within budget.

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 two-parameter, read-only list tool with full schema coverage and no output schema, the description covers what is retrieved, that results are paged, and how the payload is shaped ('same shape as invoices'). The only gap is pagination termination behavior (no indication of whether a total count is returned).

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%: limit (default 100, max 500) and offset are fully documented in the schema. The description only echoes 'paged' and adds no format, default, or semantics beyond that, so baseline 3 applies.

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 the resource (sales quotes) and the operation (list/paged) unambiguously, and adds the useful cross-reference 'same shape as invoices'. It does not need to differentiate from siblings since no other quote tool exists in the sibling list, but it also never explicitly says 'retrieve' or contrasts with invoice listing.

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?

'All sales quotes' implies this is the unfiltered enumeration tool, and 'paged here' hints at iterating pages. However there is no explicit when-to-use statement, no note on when a caller would prefer an invoice-based tool, and no guidance on how to terminate pagination.

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