Akakçe favorite remove

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

No annotations are provided, so the description carries the full burden. It does disclose the critical auth prerequisite ('Giriş gerektirir'), which is genuinely useful, but says nothing about reversibility, idempotency, or what happens if the product is not in the list.

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?

Three short sentences: action first, then parameter sourcing, then the auth prerequisite. Zero filler and front-loaded.

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 two-required-param mutation with no output schema, the description covers the action, parameter sourcing, and the login requirement. Only failure modes and effect of a missing product are absent.

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 100%, so baseline is 3; the description earns above baseline by explaining how to obtain the listId via akakce_favorites, which the schema does not say. Both required params are acknowledged, though their types and semantics remain entirely in 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?

States a specific verb and resource: 'Bir ürünü favori listesinden çıkarır' (removes a product from the favorites list). The removal framing distinguishes it from the sibling akakce_favorite_add, though it does not name that sibling directly.

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?

Gives concrete operating guidance by naming where listId comes from ('listId'yi akakce_favorites'ten al'), effectively routing the agent to the sibling that produces the prerequisite value. It does not state explicit when-not-to-use conditions, which keeps it below a 5.

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