List leads

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuine behavioral context by disclosing pagination and the cursor/nextCursor contract, which is beyond the annotations, but it says nothing about auth requirements, rate limits, or default/max page size.

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 tight sentences with the resource and filter semantics front-loaded and no filler. The parenthetical filter dump is dense but every clause earns its place, aside from the slightly cramped phrasing of the pagination clause.

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?

No output schema exists, but the description explains the return-time pagination contract (cursor from nextCursor), which is the key missing piece. The main residual gap is limit/default page size and lack of any sibling routing guidance for a tool with 20 siblings.

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%, so the description carries the full burden, and it does most of the work: it defines the score range (0–100), the sentiment enum values, converted semantics, and that q searches handle/name and tag is a tag id. It omits meaning for limit and only partially explains cursor, so it is strong but not complete.

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+resource ('List/filter leads') and notes it is paginated. It does not explicitly differentiate from siblings like export_leads or get_lead, though the list/filter framing implicitly separates it from the single-lead getter.

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 filter list implies when to use it (browse/segment leads), but there is no explicit when-to-use vs when-not guidance or named alternative such as export_leads or get_lead. Usage is implied rather than stated.

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