wafeq_items_create

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

The description discloses that the operation is a non-idempotent write, explains the effect of calling twice, and documents the idempotency_key behavior and auto-generated UUID. Annotations provide readOnlyHint=false, idempotentHint=false, destructiveHint=false, and the description adds meaningful behavioral context beyond those flags.

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 with the endpoint, resource, and safety warning. The line breaks and emojis make it scannable, though the '🟡 WRITE' prefix and 'Create item' title add a bit of redundancy with the annotations.

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?

The description covers the key behavioral concern (non-idempotency and retry safety) and confirms the endpoint. There is no output schema, but for a create endpoint the response is reasonably inferable; it could mention that a created item object is returned, but this is a minor 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?

The input schema already provides detailed descriptions for all parameters (100% coverage), including nested units of measure and idempotency_key header behavior. The description adds value by explicitly mentioning idempotency_key and the automatic retry safety mechanism, but most parameter semantics are already in the schema.

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 tool creates data via POST /items/, specifies the resource (Items), and identifies it as a write operation. The title 'Create item' and the explicit 'creates data · Items · POST /items/' line distinguish it from retrieval, update, and destroy siblings.

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 states this is the endpoint for creating a new item and explicitly warns it is not idempotent, advising use of idempotency_key for safe retries. It doesn't explicitly name alternative tools for creating items (e.g., why not use item_units_of_measure_create), but the resource and action are unambiguous.

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