delete_search_view

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

With no annotations provided, the description clearly discloses the destructive action and the conditional removal of refined turns referenced by the view. It also provides a rationale for the flag, though it does not mention irreversibility or permission requirements.

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 consists of two efficient sentences: the primary action is front-loaded, and the optional behavior is explained in the second sentence. There is no filler or redundant detail.

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?

Given the low complexity, the description covers the core behavior and optional side-effect while the schema handles parameter details. It omits guidance on locating view keys (e.g., via list_search_views) and on the permanence of deletion, but these are not critical for a simple delete operation.

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 already documents both parameters with 100% coverage, so the baseline is 3. The description adds only the rationale 'purging low-quality refined data' for deleteRefinedTurns and does not add information about the key parameter 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?

The description states a specific verb ('delete') and resource ('saved search view'), making the tool's function clear and unambiguous. It also mentions the optional deletion of refined turns, which helps distinguish it from generic sibling tools like 'delete'.

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 implies this tool should be used to delete saved search views but gives no explicit guidance on when to use it versus alternatives or exclusions. The only usage direction is for the optional deleteRefinedTurns flag, not for selecting this tool over others.

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