rozetka_saved_search_create

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

No annotations, so the description carries the full behavioral burden. 'Save locally' usefully signals client-side persistence rather than server state, but it omits whether an existing name is overwritten, whether a handle/id is returned for rozetka_saved_search_run, and any validation or storage-limit behavior.

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?

One tight sentence with the verb and purpose front-loaded and no filler. It is lean, though the brevity is part of why other dimensions are thin.

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?

A mutation tool with no annotations and no output schema, wrapping a nested search object with 9 sub-fields. The description says nothing about what is returned, how the saved search is later referenced by run/delete/list, or how it interacts with name collisions, leaving an agent under-informed.

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?

Top-level schema description coverage is 0%: neither 'name' (uniqueness, overwrite semantics) nor the 'search' object is explained in the description beyond the word 'structured'. With low coverage the description should compensate, and it does not, even though the nested schema partially self-documents.

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 (save) and resource (a structured Rozetka search) plus the intent (repeat execution), which separates it from rozetka_search_products (one-off search) and rozetka_saved_search_run (execute a saved one). It stops short of naming those siblings explicitly, so an agent still has to infer the boundary.

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?

'For repeat execution' implies the condition for using it over a direct search, but there is no explicit when-to-use statement, no mention of the companion tools (run/list/delete), and no note on prerequisites or exclusions.

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