wafeq_purchase_orders_bill_create

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

The description goes beyond the annotations by disclosing that the result is a draft bill, that the operation is non-idempotent ('calling twice creates two records'), and that passing an idempotency_key makes retries safe. These statements are consistent with annotations (readOnlyHint=false, idempotentHint=false) and add useful operational safety 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 header line is compact and informative, but the non-idempotency warning is stated twice nearly verbatim ('Not idempotent — calling twice creates two records...' and 'Calling twice creates two bills — pass an idempotency_key if you may retry'), adding redundancy without introducing new information.

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 simple one-parameter tool, the description covers the core behavior, the draft-bill state, and the retry risk. Gaps remain: idempotency_key is referenced but not present in the schema, and the description does not say what happens to the source purchase order after conversion or what the response contains (and there is no output schema to fill that gap).

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 does clarify that the only schema parameter, id, identifies the purchase order, via the endpoint URI and the 'Convert purchase order to bill' phrasing. However, it repeatedly references an idempotency_key that is absent from the input schema, leaving ambiguity about how the agent is expected to supply it.

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 states a specific verb and resource: 'Convert purchase order to bill' and 'Creates a NEW draft bill from the purchase order,' and it includes the endpoint path POST /purchase-orders/{id}/bill/. What the tool does is unambiguous, though it does not explicitly contrast itself with the sibling wafeq_bills_create (which creates a bill from scratch), leaving that differentiation implicit.

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 intended use case ('convert a purchase order to a draft bill') is clearly implied by the description and endpoint path. However, there is no explicit when-to-use vs when-not-to-use guidance, and no alternative tool such as wafeq_bills_create is mentioned, which an agent could otherwise confuse as a substitute path to the same result.

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