İade Red Nedenleri (getClaimsIssueReasons)

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

Without annotations, the description provides valuable behavioral context by noting that reason 1651 cannot be selected within the first 24 hours after WaitingInAction. This is a key constraint that helps the agent avoid errors.

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 two sentences with no wasted words. The main purpose is front-loaded, and the note adds essential information efficiently.

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 no output schema, the description could hint at the return format (e.g., includes claimIssueReasonId), but it is sufficient for the agent to understand the tool's output is a list of reasons. The behavioral note adds depth.

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?

The tool has no parameters, and schema coverage is 100%. The description does not need to add more, so baseline 4 is appropriate.

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 lists valid rejection reasons (red nedenleri) for trendyol_create_claim_issue, using specific verb 'listeler' and resource, distinguishing it from sibling claim tools.

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 ties the tool to trendyol_create_claim_issue, implying it is a prerequisite. It does not explicitly state when not to use or mention alternatives, but the context is clear.

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