get_lead_lists

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

No annotations are provided, so the description carries the full burden. It adds value by disclosing the subscription requirement, which is a behavioral trait (authentication/access need). However, it lacks details on rate limits, pagination behavior beyond the schema, or what the return format looks like, leaving gaps in behavioral context.

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 a single, efficient sentence that directly states the tool's purpose and a key requirement. It is front-loaded with essential information and contains no unnecessary words, making it highly concise and well-structured.

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?

Given the tool's moderate complexity (list retrieval with pagination), no annotations, and no output schema, the description is somewhat incomplete. It covers the basic purpose and a prerequisite but lacks details on output format, error handling, or behavioral nuances, which could hinder effective agent use.

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?

The schema description coverage is 100%, with both parameters ('start' and 'count') clearly documented in the schema. The description does not add any meaning beyond this, such as explaining pagination strategies or constraints, so it meets the baseline score for high schema coverage without extra value.

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 clearly states the verb 'Get' and resource 'all lead lists from Sales Navigator', making the purpose unambiguous. However, it does not explicitly differentiate from sibling tools like 'get_lead_list_members' or 'get_saved_leads', which might involve related data, so it falls short of a perfect score.

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 provides some context by mentioning 'requires Sales Navigator subscription', which implies a prerequisite for use. However, it does not specify when to use this tool versus alternatives like 'get_lead_list_members' or 'get_saved_leads', nor does it outline any exclusions or specific scenarios for application.

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