rozetka_saved_search_delete

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

With no annotations, the description carries full behavioral burden. It discloses only that the saved search is 'local', which usefully implies no remote/server-side effect, but says nothing about irreversibility, error behavior for an unknown id, or whether other saved searches are affected.

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?

A single short sentence with no filler, and the action is front-loaded. It is efficient, though arguably too terse for the gaps it leaves.

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 destructive-looking operation with no annotations, no output schema, and an undocumented id parameter leaves key information missing: where the id comes from, whether deletion is permanent, and what happens on failure. The description is inadequate for a delete tool.

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 0% and the description never mentions the single required 'id' parameter, so it does not tell the agent what the id identifies or where to obtain it (e.g., from rozetka_saved_search_list). The schema supplies only type and minLength constraints.

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 ('Delete') and resource ('locally saved Rozetka search'), which is unambiguous against siblings like rozetka_saved_search_create/run/list. It does not explicitly contrast itself with those siblings, but the action and target are 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?

There is no guidance on when to use this versus alternatives, nor on prerequisites such as obtaining the id from rozetka_saved_search_list before deleting. The word 'locally' faintly scopes the operation but no explicit when/when-not is given.

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