get_open_quotations

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

Since no annotations are provided, the description carries the behavioral burden. 'List' implies a read-only operation, but the description does not mention pagination, default limits, result ordering, or any data-freshness caveats. It adds some useful behavioral context with the optional customer filter, but leaves significant gaps.

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 sentence that front-loads the action and resource, adds the key filtering option, and contains no filler. Every word earns its place.

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?

The tool is simple, with only two optional parameters and no output schema, but the description still leaves topN semantics and the expected return shape undefined. It is adequate for a basic list operation, but not fully complete without those details.

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 0%, so the description must compensate. It correctly explains that cardCode filters by customer, but it gives no meaning to topN beyond the property name; a number called 'topN' is not enough to know whether it limits rows, controls sort order, or applies some other behavior.

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'), a clear resource ('open sales quotations from SAP B1'), and notes an optional customer filter. This clearly distinguishes it from siblings like create_sales_quotation (creation) and get_open_orders (orders, not quotations).

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 makes the primary use case explicit: retrieving open sales quotations, optionally narrowed by customer. It provides clear context for when to call it, though it does not explicitly name alternatives or state when not to use it.

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