İade Kalemlerini Onayla (approveClaimLineItems)

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

With no annotations provided, the description fully discloses behavioral traits: approval is irreversible and starts the refund process. It also notes potential status change to WaitingFraudCheck if fraud control applies. The warning symbol (☢️) emphasizes the destructive nature.

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, front-loaded with the critical warning. Every sentence adds necessary information without redundancy or fluff.

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 covers prerequisites, status constraints, and irreversible side effects. However, it lacks any indication of the response format or return values, which would be helpful since there is no output schema. The mention of possible WaitingFraudCheck status partially compensates.

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%, but the description adds value by instructing where to get claimId and claimLineItemIdList from trendyol_get_claims response and how the list maps from items[].claimItems[].id. However, the optional 'params' field is only described as 'Ek parametreler' without further explanation, leaving some ambiguity.

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 approves refund items that have reached the warehouse, using the verb 'onaylar' (approves). It specifies the resource (iade kalemleri) and distinguishes from siblings like trendyol_create_claim and trendyol_get_claims by focusing on approval of existing claims in WaitingInAction status.

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 provides explicit conditions: only claims in WaitingInAction status can be approved. It instructs users to obtain claimId and claimLineItemIdList from trendyol_get_claims response and explains the mapping. It also warns that approval is irreversible and initiates refund, giving clear when-to-use guidance.

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