teamleader_quotations_list

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

No annotations are present, so the description carries the full burden. It does not disclose pagination behavior, output shape, or explicitly confirm the operation is read-only, leaving the agent to infer from the schema's page/page_size parameters.

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 a single, front-loaded sentence that states the action and the optional filter without redundancy.

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?

A very short description for a simple list tool, but it omits any information about pagination, the response format, or the distinction between listing and retrieving a single quotation. Given the absence of an output schema and annotations, this is insufficient for an agent to fully anticipate behavior.

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 already describes deal_id and page_size (67% coverage); the description adds no new parameter semantics beyond repeating the deal_id filter and clarifies it is optional. The 'page' parameter remains undocumented, and the description does not compensate.

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 uses a specific verb ('List') and a clear resource ('quotations'), and mentions an optional filter by deal id. This distinguishes it from sibling tools like teamleader_quotations_info, create, and update.

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 implies usage as a listing endpoint via the verb 'List' and the optional deal_id filter, but it does not explicitly state when to prefer this over teamleader_quotations_info or other sibling tools, nor does it provide exclusions or alternatives.

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