Marka Listesi (getBrands)

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

No annotations provided, but the description covers key behavioral aspects: paginated results via page/size parameters, indication that it returns a list of brands, and mention of typical page size. It does not describe any destructive effects, which is appropriate for a read-only tool.

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?

The description is two concise sentences, front-loaded with the primary purpose, followed by a usage tip. No extraneous words.

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 (2 parameters, no output schema, no nested objects), the description provides all necessary information: what it does, how pagination works, typical page size, and a sibling alternative. It is fully 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 coverage is 50% (only size has description). The description adds meaning by explaining that parameters control pagination, with defaults (page=0, size=1000) and that a page can contain at least 1000 brands. This enriches understanding beyond the schema.

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 a paginated list of brands (Trendyol marka listesini sayfalı olarak döndürür) and explains the purpose of brandId. It also distinguishes itself from the sibling trendyol_get_brand_by_name, making the purpose crystal clear.

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 explicitly advises when to use this tool (for paginated brand listing) and when not to (for a specific brand, use trendyol_get_brand_by_name). It also mentions that a page can return at least 1000 brands, providing practical guidance.

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