create_sales_quotation

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Create', which signals mutation, but it does not disclose side effects, document status, validation rules, numbering behavior, permission requirements, or what happens after creation.

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 unnecessary words. It is concise and easy to parse, though the brevity comes at the cost of behavioral and parameter detail.

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?

This is a mutation tool with 6 parameters, no output schema, and no annotations, so one sentence is not enough for an agent to invoke it correctly. The description omits return behavior, meanings of optional fields, and any caveats around dates, pricing, or warehouse codes.

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 only 33%, so the description must compensate for the missing parameter documentation. It names 'customer and line-item inputs', which roughly maps to cardCode and lines, but it does not explain optional parameters like docDate, comments, docDueDate, or discountThresholdPct, leaving the agent without sufficient semantic information.

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 verb 'Create' and the specific resource 'SAP Business One sales quotation', and it mentions the core inputs: customer and line-item inputs. It does not explicitly distinguish this tool from sibling tools like create_sales_order or create_purchase_quotation, but the resource is specific enough to be understandable.

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 the tool is used when creating a sales quotation from customer and line-item data, but it gives no explicit guidance on when to prefer this tool over alternatives such as create_sales_order or create_purchase_quotation. There are no stated prerequisites, exclusions, or follow-up recommendations.

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