delete_search_query

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that a saved search query is deleted, but does not indicate whether deletion is permanent, requires confirmation, or has side effects on related data. This lack of transparency could lead an agent to misuse the tool.

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 front-loaded sentence with no wasted words. It states the essential action and resource efficiently, making it easy to parse.

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 delete operation with no annotations and no output schema, the description is too sparse. It fails to mention that deletion is likely irreversible, any necessary permissions, or what happens after the operation. This is a significant gap for a mutation tool, making the description incomplete for an agent deciding whether and how to invoke it.

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 input schema has 100% coverage for the single 'id' parameter, but the description itself adds no additional meaning beyond the schema's generic 'ID of the resource.' The schema already documents the parameter, so the baseline of 3 is appropriate, though more specific parameter context (e.g., tying the ID to a saved search query) would improve it.

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 uses a specific verb ('Delete') and resource ('saved search query'), clearly distinguishing it from sibling tools like create_search_query, get_search_query, and update_search_query. It is unambiguous about what operation is performed.

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?

No guidance is given on when to use this tool versus alternatives, nor are any prerequisites or contextual conditions mentioned. The description simply states the action without explaining when deletion is appropriate or what constraints apply.

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