wafeq_purchase_orders_create

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

Annotations already provide readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description goes beyond annotations by explicitly stating 'Not idempotent — calling twice creates two records' and explaining the idempotency_key header mechanism. This adds meaningful behavioral context about retry safety and duplicate creation. No contradiction with annotations.

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 compact and front-loaded: the emoji marker, action type, endpoint, and one-line summary appear first. The idempotency clarification follows as important behavioral context. It is slightly redundant with the title and annotations ('write', 'creates data'), but the endpoint and idempotency notes earn their 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?

This is a complex creation tool with nested objects and no output schema. The description covers the essential creation semantics and idempotency behavior, which are the most critical operational concerns. It does not describe required fields (currency, line_items) or response format, but those are adequately documented in the input schema, and the annotations cover the write intent.

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 100%, so the schema fully documents all parameters and nested line_items fields. The description adds value by explaining the idempotency_key parameter's behavior beyond the schema, including the header name and the automatic UUID v4 generation, which is genuinely useful for an agent deciding whether to pass it. The description also confirms the body's role as the purchase order payload.

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 ('creates data'), resource ('Purchase Orders'), and endpoint (POST /purchase-orders/). It explicitly differentiates this creation tool from siblings like wafeq_purchase_orders_update, wafeq_purchase_orders_line_items_create, and wafeq_purchase_orders_bill_create by focusing on creating a top-level purchase order.

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 identifies this as the endpoint for creating a new purchase order, which implies the primary use case, but does not explicitly contrast with wafeq_purchase_orders_bill_create or wafeq_purchase_orders_line_items_create. It does provide guidance on idempotency usage for retries, which helps an agent decide how to safely invoke the tool. Missing explicit when-not-to-use guidance.

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