İade Talebi Oluştur (createClaim)

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

No annotations are provided, so the description must fully disclose behavioral traits. It states the claim opens in "Created" status and mentions a stageMode parameter for environment awareness. However, it does not describe side effects, authentication requirements, rate limits, or whether the operation is reversible. Partial transparency but insufficient for a create tool.

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 a single paragraph of five sentences. It is front-loaded with the tool's purpose, then details usage conditions and parameter guidance. It is concise and avoids redundancy, though structuring with bullet points could improve readability.

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 6 parameters, no output schema, and no annotations, the description provides decent context: customerId source, stageMode, and links to related tools. However, it omits response format, error handling, and parameter constraints (e.g., valid shipmentCompanyId values). A more complete description would improve agent confidence.

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%, so baseline is 3. The description adds context for customerId (source from orders), indicates optional parameters (excludeListing, forcePackageCreation) are not sent if omitted, and explains the default reasonId (401). These additions are helpful but not extensive, so the score remains at the baseline.

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 creates a claim for packages arriving without a return code. The verb "oluşturur" (creates) and resource "iade talebi" (claim) are specific. It distinguishes from siblings like trendyol_approve_claim_items and trendyol_get_claims.

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?

The description explicitly states only use for claims you will approve ("yalnızca ONAYLAYACAĞINIZ iadeler için kullanılmalıdır"). It provides guidance on obtaining customerId from trendyol_get_orders and suggests using trendyol_get_claims to view the created package. Does not explicitly mention when not to use or list alternatives, but the guidance is clear.

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