run_hepsiburada_categories

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose useful non-schema behavior: the returned field set (id, name, alias, level, url), the nesting/child structure, and a flat 5-credit cost per successful run. It says nothing about permissions, rate limits, or error cases, so the burden is only partly met.

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?

One front-loaded sentence: the action and resource come first, then the return shape, then the cost note. Every clause is informative; the parenthetical field list is the only part that could be trimmed if an output schema existed.

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?

With no annotations and no output schema, the description does the work of describing the return structure (path plus nested children and their fields) and the cost. It lacks any error/edge-case behavior, but for a single-parameter read tool it is close to complete.

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 description coverage is 100% and the single parameter already documents 'Category ID or URL. e.g. 371965'. The description restates this ('for a category id or URL') without adding format or constraint detail, so it neither helps nor hurts beyond the schema baseline.

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?

Specific verb + resource (get the Hepsiburada category tree) and it spells out exactly what the tree contains: path from top-level department down to category plus nested children. It identifies the platform, which separates it from the many other *_categories tools, but it does not explicitly distinguish itself from its closest sibling run_hepsiburada_categories_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?

No when-to-use or when-not-to-use guidance; the only implicit signal is the 'for a category id or URL' input framing. It never tells the agent to prefer this over run_hepsiburada_categories_products when the goal is browsing the taxonomy versus listing products.

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