delete_query

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

The description goes beyond the destructiveHint annotation by explaining the deletion is non-permanent ('text is kept in a snapshot') and how to recover it. This gives the agent meaningful behavioral context about the consequences of calling 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?

Two sentences, front-loaded with the primary action followed by the recovery caveat. No wasted words; every sentence adds essential information.

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?

The description covers the main action and recovery behavior, but omits the `dry_run` parameter, which is likely important for safe previews of a destructive operation. Without output schema or parameter explanations, this is a notable gap for an agent to call the tool correctly in all modes.

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 description coverage is 0%, and the description does not explain either parameter. The `query` parameter is inferable from the tool's purpose, but `dry_run` is completely unexplained; with no schema descriptions, the agent must guess its meaning.

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 ('Remove') and resource ('a query from the library'), and clarifies the deletion is recoverable via snapshot. The mention of restore_snapshot differentiates it from a permanent deletion tool, leaving no ambiguity about what the tool does relative to siblings.

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?

Provides clear context: use this to remove a query while retaining recoverability, and points to restore_snapshot as the way to bring it back. While it doesn't explicitly state exclusions or alternatives, the context is sufficient for an agent to know when this tool is appropriate.

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