run_trendyol_categories

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the tree depth (10 departments), the nested structure, the returned field set, and an unusual cost trait ('5 point per returned record') that an agent cannot get from structured fields. It stops short of noting auth requirements or whether the full-tree call is expensive.

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?

Two tight sentences, front-loaded with what the tool returns before the invocation note. Every clause earns its place, including the billing note, and nothing is padded.

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?

For a single-optional-parameter listing tool with no output schema, the description adequately covers both the return shape and the subtree-vs-full-tree behavior, so an agent can call it correctly. It leaves minor gaps on auth and pagination/cost scaling, but nothing essential for correct invocation is missing.

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% and the schema already documents the parameter, its optionality, examples (elektronik or 5), and the empty-value behavior. The description's 'pass a category id or alias to get just that subtree' restates the schema with a light behavioral framing but adds no new syntax or format detail, so the baseline 3 applies.

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?

States a specific resource ('Trendyol category tree') and describes its shape: 10 departments with nested subcategories and the fields returned (id, name, alias, parent id, URL). The platform name plus 'categories' clearly separates it from sibling category tools like run_olx_categories or run_craigslist_categories, though it never states the action as an explicit verb.

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 explains how to invoke it ('Pass a category id or alias to get just that subtree'), which is usage guidance for the parameter rather than for tool selection. It names no alternative and gives no when-not condition, so an agent must infer that this is the entry point for Trendyol category lookups.

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