akakce_favorite_addAdds one or more product codes to your default Akakçe favorites list, requiring an authenticated session so you can save items for later.
Bir veya daha fazla ürünü favorilere (varsayılan listeye) ekler. Ürün kod(lar)ını ver. Giriş gerektirir.
| Name | Required | Description | Default |
|---|---|---|---|
| codes | Yes | Eklenecek ürün kodları |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the behavioral burden. It discloses the mutation scope, batch capability, default list target, and login requirement, but it omits what happens when a product is already favorited, whether the operation is idempotent, and what the response contains.
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 short and front-loads the purpose before giving input and authentication notes. The sentence telling the caller to provide product codes is somewhat redundant with the schema, but overall it is appropriately sized.
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 simple one-parameter mutation, the description covers purpose, authentication, and target list. It leaves notable gaps around duplicate handling and the result of the operation, and there is no output schema or annotation coverage to fill those gaps.
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 schema fully documents the single 'codes' parameter, including its array type and minimum item count. The description reinforces that product codes may be singular or plural, but adds no format or validation details beyond the schema, so the baseline 3 is appropriate.
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 states a specific verb and resource: it adds one or more products to favorites, with the default list explicitly named. This clearly separates it from removal or listing operations by behavior, though it does not explicitly name the sibling 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?
The description gives a key prerequisite, 'Giriş gerektirir' (requires login), and clarifies that the target is the default favorites list. However, it does not state when to prefer this over akakce_favorites or akakce_favorite_remove, so usage is implied rather than fully guided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.