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

With no annotations, the description carries the full behavioral burden. It discloses that the operation is free, owner-scoped, server-side sorted/filtered, and that each row includes a 'url' for the X thread, plus the return shape. However, it omits auth requirements, rate limits, and explicit read-only behavior, leaving some 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?

The description is front-loaded with the core action, then methodically enumerates parameter semantics. It is dense and slightly long, but every clause adds useful information for invoking the tool correctly, with no filler.

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 13-parameter tool with no annotations and very low schema coverage, the description covers most parameters and the return shape. It still lacks usage guidance relative to alternatives and omits auth details beyond 'owner-scoped', leaving it adequate but not fully complete.

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 only 8%, so the description must compensate, and it does so extensively: it documents query_id (including 'adhoc'), status values, min_score range, sort_col and sort_dir options, search regex behavior, date_from/date_to binding to date_field, and page/page_size constraints. It does not cover npub or dpop_token, but npub is described in the schema and the remaining parameter semantics are rich.

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 states a specific verb ('Page through') and resource ('your stored conversation leads'), and adds scope details ('server-side sorted and filtered'). It clearly distinguishes this listing tool from a simple find or query-listing operation, so an agent can identify its role without opening the schema.

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 explains what the tool does but gives no explicit guidance on when to use it versus siblings like find_conversations or list_conversation_queries. It mentions 'Free, owner-scoped' as context, but there are no when-to-use conditions, exclusions, or named alternatives.

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