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

With no annotations provided, the description carries the full burden. It usefully discloses record structure and, notably, the cost model ("5 point per returned record"), which is real behavioral context an agent cannot get from the schema. It stops short of stating auth/permission requirements or explicitly confirming the operation is read-only, but the retrieval nature is strongly implied.

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 compact sentences, front-loaded with the resource and return shape, then the filtering behavior, then cost. No filler. The final cost fragment is terse but earns its place by surfacing a billing constraint.

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 read tool with no output schema and no annotations, the description covers the key facts: what the tree contains, the fields in each node, the subtree filtering behavior, and the per-record cost. Only minor gaps remain (auth requirements, whether the full tree is paginated or returned in one shot).

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%, so the single optional "category" parameter is already fully documented with examples ("elektronik or 5") and the empty behavior. The description's note to pass an id or alias largely restates what the schema already conveys, so it adds little beyond the 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?

The description names a specific verb+resource ("Trendyol category tree") and even enumerates the returned fields (id, name, alias, parent id, URL), so an agent immediately knows what comes back. It distinguishes itself from its Trendyol siblings (products, sellers) by the resource name, though it never explicitly contrasts itself with the other platform category tools.

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" gives an implied usage mode for the optional parameter, and the schema adds the empty-string case for the full tree. However, there is no when-to-use/when-not-to-use guidance and no naming of alternatives among the many category-tree siblings. Adequate but thin.

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