Stok ve Fiyat Güncelle (updatePriceAndInventory)

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

No annotations provided, so description fully bears the burden. It reveals the tool is mutating, warns about a specific deduplication error, and explains that batch status field is not returned for stock-price updates, requiring item-level status checks. This is highly transparent.

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?

Description is a single paragraph of 4 sentences, front-loaded with purpose, then limit, clarification, warning, and follow-up. Clear and efficient, though could be slightly more concise.

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?

Tool has simple structure (one parameter with array of objects, no output schema). Description covers purpose, quantity meaning, duplication risk, and follow-up tool. Implies asynchronous behavior via reference to batch result. Lacks explicit mention of output format but sufficient given low complexity.

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%, but description adds meaning for 'quantity' (satılabilir stok) and warns not to send unchanged data. It does not elaborate on barcode or prices beyond the schema's minimal descriptions. Repeats maxItems limit already in schema. Adds some value but not comprehensive.

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?

Description clearly states the verb 'günceller' and resource 'onaylı ürünlerin stok ve fiyatı'. It also specifies a per-request limit of 1000 SKU, distinguishing it from sibling tools like trendyol_filter_approved_products_inventory_and_price.

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?

Provides important guidance: clarifies quantity meaning, warns against resending unchanged data (15-minute deduplication error), and directs to use trendyol_get_batch_request_result for result checking with a note about batch status. Does not explicitly state when not to use, but the warning implies avoidance of duplicate identical requests.

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