Ürün Oluştur (createProducts)

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

No annotations provided, so description carries full burden. Discloses max 1000 items, variant handling (same productMainId, different attributes), batch request ID requirement, and that products enter an approval process and are not published automatically. Lacks details on rate limits or authentication, but covers key behaviors.

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?

Single paragraph, but efficiently covers preconditions, variant handling, batch ID, and follow-up. Could be slightly more structured (e.g., bullet points) but no redundant sentences. Concisely packed with essential info.

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 tool complexity (nested array with many fields) and no output schema, description adequately covers variant logic, batch result checking, and approval implications. Does not describe error handling or all fields (covered by schema), but overall complete for usage.

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 coverage is 100% with field descriptions. Description adds context beyond schema: explains variant usage (same productMainId), that cargoCompanyId must be approved, and that attributes can be either attributeValueId or customAttributeValue. This adds meaningful guidance.

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 uploads single/bulk products to Trendyol with a max of 1000 items per request. It distinguishes from sibling tools like trendyol_update_price_and_inventory or trendyol_update_approved_product_content by focusing on creation and referencing prerequisite tools for IDs.

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?

Explicit preconditions are given: must first call trendyol_get_brands, trendyol_get_category_tree, etc. to get required IDs. Also specifies follow-up action: call trendyol_get_batch_request_result to check result. Notes that products are not automatically published but go through approval. Does not explicitly state when NOT to use, but context is clear.

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