run_trendyol_sellers

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

With no annotations, the description carries the full behavioral burden, and it does add one real trait: the 'Flat 5 points per successful run' cost disclosure. However it omits other behavioral context such as permission requirements, rate limits, or whether the lookup fails on a bad URL. 'Get' implies a read, but nothing else is stated.

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?

Two tight sentences with the resource and accepted inputs front-loaded, followed by the returned fields and the cost note. Nothing is redundant or padded.

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-parameter read tool with no output schema, the description usefully enumerates the returned fields (name, city, score, product count, verified status, shipping/response metrics), which compensates for the missing output schema. It only falls short on usage routing among siblings.

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% and there is a single parameter, so the baseline is 3. The description restates the accepted input ('id or store URL') but adds no syntax, format, or fallback detail beyond what the schema already provides.

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?

States a specific verb and resource ('Get one Trendyol seller (store) by id or store URL') and enumerates the returned fields, so the agent knows exactly what it retrieves. It does not name any sibling tool, so differentiation from run_trendyol_sellers_products or run_trendyol_products_sellers is left to inference, which keeps it out of 5 territory.

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?

No when-to-use, when-not-to-use, or alternative-tool guidance is given. The agent must infer from the name alone that this returns a single seller rather than listing sellers or their products, which is a notable gap given the dense Trendyol sibling set.

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