delete_saved_search

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

With no annotations, the description carries full responsibility for behavioral disclosure, but it only says 'delete'. It does not convey that this is an irreversible destructive action, whether associated alerts are also removed, or if any confirmation is required. A delete operation warrants more transparency.

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 a single, direct sentence with no filler. It is fully front-loaded and concise, though perhaps too terse for the required context, the structure itself is exemplary.

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 destructive tool with no annotations, the description is far too sparse. It omits irreversible effects, parameter guidance, and usage context. Even though an output schema existsathe agent cannot safely invoke this without more information about consequences and identification.

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 has a single required parameter 'name_or_id' with zero description coveragehola. The tool description does not explain how to specify the saved search, what format name_or_id accepts, or how to obtain valid values (e.g., via list_saved_searches). The property name hints at accepting a name or ID, but the description adds no meaning beyond 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?

The description 'Delete a saved search.' states a specific verb ('delete') and resource ('saved search'), clearly distinguishing it from siblings like create_saved_search, list_saved_searches, and run_saved_search. The purpose is immediately obvious and unambiguous.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no mention of effects like whether the search must exist or whether deletion is permanent. An agent gets no contextual help beyond the literal action.

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