Onaylı Ürün Varyantlarını 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 batch limit, non-updateable barcode, and partial update support. But it does not detail whether the operation is synchronous or asynchronous, nor error behavior. Adequate but not comprehensive.

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?

Two sentences, front-loaded with purpose, then key details. No wasted words; efficient and well-structured.

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 mentions checking batch result but does not describe output schema or expected response format. For a mutation tool, it provides basic flow but lacks completeness.

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% (based on context), and the description only adds value for the barcode parameter (non-updateable). It does not explain other nested fields, leaving significant ambiguity for the agent.

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 it updates variant information of approved products with a batch limit of 1000 items. It uses a specific verb ('günceller') and resource ('onaylı ürün varyantları'), distinguishing it from sibling tools like trendyol_filter_approved_products or trendyol_update_approved_product_content.

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 explains that all fields except barcode can be updated and that partial updates are supported, guiding when to use. It also directs checking the batch request result for status. However, it does not explicitly compare to alternative tools or state when not to use it.

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