Marka Ara (getBrandsName)

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

With no annotations, the description adds a critical behavioral detail (case sensitivity). However, it does not disclose other traits such as what happens when the brand is not found (e.g., error vs empty result) or any 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?

The description is extremely concise: one sentence stating purpose immediately followed by a critical warning. No wasted 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?

The description covers the basic usage but omits details on return values, error handling, or how results are structured. Given the tool's simplicity, it is minimally adequate but not 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?

The input schema already provides 100% coverage with a description matching the tool's. The description adds an example ('TRENDYOLMİLLA') but does not substantially enhance meaning 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 the tool's action ('searches by brand name') and resource ('brand'). While it doesn't explicitly differentiate from sibling 'trendyol_get_brands', the name and context imply a specific lookup by name, making purpose sufficiently 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 warns about case sensitivity but provides no guidance on when to use this tool versus alternatives like 'trendyol_get_brands'. No usage context or exclusions are given.

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