Create Purchase Order

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds that it returns 'the create response (new PO identifier / status)' and requires certain fields, but does not elaborate on side effects or error behavior. It doesn't contradict annotations, but adds limited additional behavioral context.

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 concise and well-structured: it leads with the action, then lists required fields, gives resolution guidance, and ends with return value. Every sentence earns its place without unnecessary fluff.

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 complexity (11 parameters, nested objects, no output schema), the description covers required fields, resolution strategy, the return payload, and the additional_fields escape hatch. It's well-aligned with the schema and provides sufficient context for an agent to invoke it correctly.

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 coverage is high (82%), but the description adds meaning by listing required fields, advising to resolve certain identifiers via lookup tools, and explaining that 'Other fields via additional_fields' serves as an escape hatch. This goes beyond the schema for those parameters.

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 opens with 'Create a new purchase (inbound) order,' a specific verb+resource that clearly distinguishes it from sibling tools like create_shipment_order and create_return_order. It also lists required fields and the return value, reinforcing the tool's purpose.

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 explicitly instructs to 'Resolve client/warehouse/type/currency with logiwa_lookup and logiwa_list_warehouses,' providing clear guidance on prerequisites and alternative tools. It doesn't explicitly state when not to use the tool, but does offer context for field resolution.

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