update_price_and_stock

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

With no annotations provided, the description carries the full burden, and it does so thoroughly. It discloses that this is a write operation, requires an environment variable to be set (refusal otherwise), processes asynchronously, and returns a batchRequestId. It also clarifies that only provided fields are updated, preventing assumptions that omitted fields are cleared. This is exemplary transparency.

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 well-structured, starting with a WRITE: label that immediately sets expectations, followed by the requirement, then the args block with an example and edge cases, and ending with the return format. Every sentence adds value; the example is illustrative without being redundant. It is slightly longer than strictly necessary but remains tight.

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 (single parameter with rich JSON semantics), the description covers all that an agent needs to call it correctly: purpose, prerequisite, item fields, optionality, batch size, async behavior, and the returned batchRequestId. The existing output schema likely documents the return shape, so not repeating it is fine. No critical gap exists.

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 defines only 'items_json' (string) with no description (0% coverage). The description fully compensates by specifying it's a JSON array of item objects, giving a concrete example, listing required and optional fields, and enforcing the max 1000-item limit. An agent can construct valid input without opening any other documentation.

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 'WRITE: batch-update stock quantity and/or prices for existing products.' This names a specific verb (batch-update), a concrete resource (stock quantity and/or prices), and scopes it to existing products. It clearly distinguishes itself from the sibling read tools (get_products, get_orders, etc.) which are all queries or single-item operations.

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?

It states the prerequisite environment variable (TRENDYOL_ALLOW_WRITES=true) that must be set for the tool to proceed, which is a direct usage condition. It also outlines the batch nature and the asynchronous result. It does not explicitly name alternatives, but the purpose is unambiguous enough that no exclusion is needed; the context is clear.

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