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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuine non-annotation context: the 'Flat 5 points per successful run' cost, which matters for tool selection. It says nothing about failure modes, empty results, or rate limits.

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?

Three short sentences, front-loaded with the output shape and then the parameter behavior and cost. No filler or restated naming.

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 output schema, the description compensates by listing the returned fields (id, name, alias, parent id, URL) and the nesting depth, which is what an agent needs to plan. Minor gaps: no indication of response size for the full tree or whether subtree results include descendants.

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 gives example values ('elektronik or 5') and the empty-default behavior. The description merely restates 'category id or alias' without adding format, case sensitivity, or invalid-id behavior, so 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?

The description names the specific resource (Trendyol category tree), its shape (10 departments with nested subcategories) and the returned fields, so the agent knows exactly what comes back. It does not explicitly contrast with sibling category tools or with run_trendyol_products, but the resource noun 'categories' disambiguates it well enough.

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?

'Pass a category id or alias to get just that subtree' implies the two operating modes (full tree vs. subtree) and the default when empty. There is no explicit when-to-use guidance, no note that this is the natural first step before run_trendyol_products filtering, and no mention of when not to call it.

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