Kategori Ağacı (getCategoryTree)

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

Discloses that the tree updates regularly and advises weekly refreshes to avoid errors. While it doesn't explicitly state read-only behavior, the description is sufficient for understanding expected behavior given no annotations are provided.

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?

Concise and front-loaded: first sentence states purpose, followed by essential usage rules and parameter behavior. Every sentence adds value without redundancy.

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 optional parameter, no output schema), the description covers purpose, usage constraints, and parameter behavior completely. No additional information is necessary for correct invocation.

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?

Adds significant meaning beyond the input schema by explaining that the 'name' parameter filters categories where the keyword appears at any level, which isn't fully conveyed in the schema description.

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 clearly states it returns the Trendyol category tree and specifies critical usage constraints (only leaf categories for product creation). It distinguishes itself from sibling tools by providing unique functionality not covered by other getters.

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?

Explicitly provides when to use (get category tree) and when not to (cannot use non-leaf categories for product creation). Recommends weekly refresh to maintain data accuracy, offering clear contextual guidance.

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