Ürün Teslimat Bilgisini Güncelle

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

With no annotations, the description carries full burden. It discloses that barcode is immutable, the fastDeliveryType constraint, and the need to check batch result via another tool, implying async behavior. This is valuable behavioral context beyond basic operation.

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 short three-sentence paragraph that front-loads the main action and includes essential constraints and follow-up. Every sentence contributes useful information, but it could be slightly more structured for readability.

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 no output schema and complex nested parameters, the description provides key missing context: barcode immutability, batch size limit, and async result checking. It lacks explanation of error handling or input structure description, but is fairly complete for a batch update tool.

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% except for deliveryDuration minimally. The description adds that all fields except barcode are updatable and the fastDeliveryType condition. However, it does not explain what deliveryDuration means (duration unit) or the meaning of fastDeliveryType enum values, leaving 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 clearly states the tool updates delivery information for approved products, with constraints like max 1000 items and barcode immutability. However, it does not explicitly distinguish it from sibling update tools for other product aspects (content, variants, price/inventory).

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 usage context (approved products, batch limit) and a specific condition for fastDeliveryType. It also mentions checking batch request result for async follow-up. But it lacks when-not-to-use guidance or explicit alternatives among siblings.

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