Siparişleri Listele

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

The description indicates the tool 'lists' orders, implying a read operation, but does not explicitly state it is non-destructive or require authentication. With no annotations, this leaves some behavioral ambiguity, though the status filters give some operational context.

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 extremely concise with two sentences, front-loading the main purpose, then listing filter values. Every sentence is essential, 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 the tool has 8 parameters and no output schema, the description adequately covers core functionality (pagination, status filter, orderNumber), but omits details on date range, sorting, and return structure. It is sufficient for a simple listing tool but not comprehensive for complex queries.

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 description adds value by enumerating the valid status values and emphasizing the use of orderNumber for specific order retrieval. It also mentions pagination. Since the schema already covers 75% of parameters with descriptions, the description's additions are meaningful but not extensive.

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 explicitly states the tool lists the seller's orders (packages) with pagination, and mentions filtering by orderNumber and status. This clearly distinguishes it from other trendyol tools like getting claims or 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?

It provides clear context on when to use the tool (list orders) and how to filter (by orderNumber, status). However, it lacks explicit when-not-to-use or alternative tool mentions, so it does not reach the highest score.

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