Get a list of quotations

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior, so the description only needs to add meaningful behavioral context. It adds pagination behavior and notes that line items are included, which is useful beyond the structured annotations. There is no contradiction with 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 short and front-loads the core purpose. The opening sentence mostly repeats the title, and the endpoint notation adds minor value, so it is not perfectly lean, but it remains concise and well-structured overall.

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 list tool with no required parameters and a fully documented schema, the description adequately covers purpose, pagination, and response content. It could mention default page size or records-per-page behavior, but nothing essential is missing for an agent to invoke it correctly.

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%, meaning all seven parameters are already documented in the input schema. The description does not add parameter-specific meaning beyond indicating that the list includes line items, so the baseline 3 is appropriate.

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 clearly states a specific action ('Get') and resource ('quotations'), then further specifies 'a paginated list of all quotations with their line items.' This distinguishes it from sibling tools like get_quotation or list_sales_invoices by making both the resource and the list behavior explicit.

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 phrasing 'Get a paginated list of all quotations' implies this tool is for enumerating multiple quotations rather than retrieving a single one, but it does not explicitly name alternatives or state when not to use it. The usage context is implied by the resource and list semantics rather than spelled out.

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