linkedin_list_lead_lists

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The verb 'List' implies a read-only operation, which is a basic behavioral trait, but it does not disclose any details about return format, pagination, authentication, or rate limits. While the safety is implied, richer behavioral context is missing.

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, front-loaded sentence: 'List all lead lists in LinkedIn Sales Navigator.' It is concise, clear, and every word contributes to the meaning. There is no redundant or filler content, making it an excellent model of brevity.

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?

The tool is simple with no parameters and no output schema, but the description still does not fully cover the context. It states the purpose but does not describe the structure of the returned data (e.g., whether it includes IDs, names, or other metadata). An agent may need to rely on external knowledge or trial and error to understand the output. Given the absence of an output schema, the description should have provided more detail about the return value.

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 input schema has zero parameters, so there are no parameter semantics to clarify. Per guidelines, a tool with 0 parameters receives a baseline score of 4 because the description does not need to compensate for missing parameter information. The description appropriately omits parameter details that do not exist.

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 uses the specific verb 'List' with the resource 'lead lists' and scopes it to 'all' in LinkedIn Sales Navigator. This clearly distinguishes it from sibling tools like 'create_lead_list' which creates lists, and 'search_leads' which searches for leads. The purpose is unambiguous and actionable.

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 no guidance on when to use this tool versus alternatives. It does not mention that it is the appropriate tool for viewing all lead lists, nor does it reference the sibling tools such as create_lead_list or search_leads. An agent receives no contextual advice for tool selection.

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