Ürün Sil

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

Despite no annotations, the description fully discloses irreversibility (geri alınamaz), conditions for deletion, and batch behavior. Instructions on follow-up result checking imply asynchronous processing.

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 with front-loaded warning, followed by conditions, alternative, and result check instruction. Every sentence adds meaningful information, no redundancy.

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 complexity (irreversible, conditional, batch, async), the description covers all key aspects: irreversibility, allowed conditions, alternative tool, and result checking. No gaps.

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?

Only one parameter (barcodes) with 100% schema description coverage. Description adds no extra meaning beyond the schema, but the schema constraints (maxLength, minLength, maxItems) are sufficient.

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 that the tool deletes products from Trendyol system ("ürün silme geri alınamaz... siler") and specifies allowed product types for deletion (onay bekleyen, arşivdeki). It distinguishes from sibling tools like trendyol_archive_products.

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?

Explicitly provides when-not-to-use (for temporary removal, use trendyol_archive_products) and mentions follow-up with trendyol_get_batch_request_result. Conditions for deletion are clearly stated.

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