teamleader_quotations_list

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the tool lists quotations. It does not mention pagination, ordering, field selection, whether only IDs are returned, or any other behavioral traits that would help an agent understand the tool's output or side effects.

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 with no filler words. Every word contributes to the purpose, and it is appropriately sized for a simple list tool.

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?

Given the tool's low complexity (one optional parameter, no output schema), the description is adequate but leaves gaps. It does not explain what the listed quotations contain, whether the list is paginated, or how the 'ids' filter affects the results. Still, for a straightforward list operation, it meets the minimum viable threshold.

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?

The input schema defines one parameter 'ids' with description 'Filter by UUIDs', giving 100% schema description coverage. The tool description itself adds no additional parameter semantics beyond the schema, so the baseline of 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 the action ('List') and the resource ('quotations'), and it names the system ('Teamleader Focus'). However, it does not explicitly differentiate from sibling tools like teamleader_quotation_info or teamleader_quotation_create, though the verb 'list' implies a collection operation.

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?

No guidance is provided on when to use this tool versus alternatives, nor on the intended use of the optional 'ids' filter. The description implies a basic listing use case but does not mention exclusions, prerequisites, or scenarios where other quotation tools would be more appropriate.

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