Satış/İade Hakedişleri (Settlements)

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

No annotations provided, so the description carries full burden. It discloses key behaviors: settlements appear only after delivery, date range auto-batching, paymentOrderId creation timing, correction entry pairing, and store* field nullability. This is comprehensive beyond the schema.

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 lengthy but efficiently packed with essential details. It is structured logically: purpose, parameter interactions, date handling, payment info, correction notes, and field behavior. For a tool with 7 parameters and complex rules, this length is justified, though slightly verbose.

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 tool has no output schema, so the description should explain return structure. It mentions store* fields and affiliate values but does not fully describe the response format or pagination. However, it covers most behavioral aspects and references other tools for detailed transaction type explanations, leaving minor 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?

Schema coverage is 100%, but the description adds significant meaning: priority of transactionTypes over transactionType, automatic 15-day slicing, paymentDate expected as string, and correction entry relationships. These details go beyond basic parameter descriptions, helping the agent use parameters correctly.

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 what the tool does: 'Satış, iade, indirim, kupon ve provizyon işlemlerinin detaylarını getirir.' It specifies the resource (settlements) and verb (get details). Among siblings like trendyol_get_other_financials, it distinguishes as the settlement-specific financial tool.

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 detailed guidance on when to use the tool: after delivery, with date range limitations (max 15 days, auto-batched), single vs multiple transaction type selection, paymentOrderId usage, and cross-references to other tools for transaction type definitions. It also explains field behavior for different seller types, giving clear context for proper invocation.

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