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

With no annotations the description carries the full burden, and it discloses two genuinely useful traits: the destructive scope is limited (leads survive and become ad-hoc leads) and the operation is 'Free and owner-scoped', implying no cost and only your own queries are affected. It omits irreversibility/confirmation and the auth role of dpop_token, keeping it short of a 5.

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 short sentences, front-loaded with the action and followed by the non-obvious consequence. No filler or restatement of the tool name.

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 mutation tool with no annotations, the description covers the key side effect (leads retained) and the cost/ownership scope, and an output schema exists so return values need not be explained. The remaining gap is the undocumented dpop_token and query_id semantics.

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 only 33% (npub is documented, query_id and dpop_token are not), so the description is expected to compensate but adds nothing about any parameter — no format for query_id, no explanation of dpop_token. The 'owner-scoped' phrase loosely gestures at npub but does not document 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?

States a specific verb ('Delete') and a precisely named resource ('saved conversation queries'), which is enough to distinguish it from the save/list conversation-query siblings without opening any schema. It stops short of explicitly naming those alternatives, so it lands at a clear-but-undifferentiated 4.

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 when-to-use or when-not-to-use guidance and no reference to the sibling tools (list_conversation_queries, save_conversation_query, find_conversations) that an agent would weigh against it. The 'leads are kept' note describes an effect rather than a condition for selecting this tool.

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