create_purchase_order

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states the creation intent and does not mention whether the PO is posted or draft, whether an existing vendor/cardCode is required, what side effects occur, or what the response contains. For a mutation tool, this is a significant transparency gap.

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 conveys the action, system, and core entities without redundant content. Every word adds signal, and there is no wasted phrasing.

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 mutation tool with no annotations and no output schema, the description is operationally incomplete. An agent cannot tell what result to expect, whether the document is saved as draft or posted, or what practical constraints apply beyond the required schema fields. The definition leaves too much unstated for reliable invocation in an ERP context.

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 description adds some parameter context by mapping 'vendor' to cardCode and 'line items' to lines. However, it provides no semantic detail for docDate, unitPrice, taxCode, warehouseCode, or itemCode, and schema description coverage is only 60%, so the description does not fully compensate for the schema's gaps.

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 ('Create') and names the exact resource ('SAP Business One purchase order for a vendor with line items'). This clearly distinguishes it from sibling tools like create_purchase_request, create_purchase_quotation, and create_sales_order, because 'purchase order' plus 'vendor' is 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 description provides no guidance on when to use this tool versus create_purchase_request, create_purchase_quotation, create_po_from_quotation, or create_goods_receipt_po. There is no when/when-not context or mention of alternatives, so the agent must infer the correct use case from the name alone.

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