Ürün Durum Bilgisi (filterProducts)

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

No annotations are provided, so the description must carry the full burden. It only describes the return value and does not explicitly state that this is a read-only operation with no side effects, nor does it mention idempotency, rate limits, or other behavioral traits. The name suggests read-only but the description lacks explicit transparency.

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 concise sentence with no wasteful words. It front-loads the action and immediately specifies the returned fields.

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's simplicity (one parameter, no output schema), the description adequately previews the output by listing the fields. It compensates for the lack of output schema. However, it could improve by explaining the meaning of each field or their data types.

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 schema already describes the single parameter 'barcode' with 100% coverage. The description merely references the barcode without adding new meaning such as expected formats, validation rules, or examples. Baseline 3 is appropriate as the schema does the heavy lifting.

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 uses a specific verb 'döndürür' and clearly specifies the resource 'tek bir barkod' and the exact fields returned (approved, archived, listingId, contentId, approvedDate). This distinctly differentiates it from sibling tools like trendyol_get_products which return full product details or trendyol_filter_approved_products which filter lists.

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 implies use for a single barcode status check but provides no explicit guidance on when to use this tool versus alternatives like trendyol_get_products or trendyol_filter_approved_products. No usage context, prerequisites, or exclusion criteria are mentioned.

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