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

With no annotations, the description carries the full behavioral burden. It does disclose two real traits: the call is free (no credits/payment) and results are scoped to the owner, plus it names the response envelope. It says nothing about auth requirements for dpop_token, pagination, or ordering, which are the remaining behavioral gaps.

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?

Three short, front-loaded sentences with zero filler: purpose first, scope/cost second, return shape last. Every sentence adds 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?

An output schema exists, so the return format need not be spelled out, and the description still names it. Cost and ownership scope are covered; the only omission is auth handling for dpop_token, which is a moderate gap for an otherwise simple read-only list tool.

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 50% (npub is documented as required; dpop_token has no description anywhere). The description adds no parameter-level meaning at all, so it fails to compensate for the undocumented dpop_token, landing below the baseline 3 given to fully covered schemas.

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 and resource ('List your saved conversation queries') plus the payload detail ('with their last-run watermarks'), which distinguishes it from list_conversations (raw conversations) and its save/delete query siblings. It does not explicitly name any sibling, so differentiation is implicit rather than stated.

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?

'Free and owner-scoped' gives useful selection context (no cost, only your own saved queries), which implies when to use it. However it never names the alternatives — save_conversation_query or delete_conversation_query — or states when this listing is the right call versus those tools.

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