get_lead_list_members

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the subscription requirement, which is useful context. However, it lacks details on pagination behavior (implied by parameters but not explained), error handling, rate limits, or what the output looks like (no output schema). For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 front-loads the core purpose and includes a key prerequisite. There is no wasted verbiage or redundancy, making it easy to parse quickly. Every word earns its place by contributing essential 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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain the return format (e.g., list of lead objects), pagination details beyond parameter names, or potential errors. For a tool with three parameters and no structured output documentation, more context is needed to fully understand its operation and results.

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 clear descriptions for all three parameters (list_id, start, count). The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 action ('Get') and target resource ('leads within a specific Sales Navigator lead list'), making the purpose immediately understandable. It distinguishes itself from siblings like 'get_lead_lists' (which retrieves lists) and 'get_saved_leads' (which retrieves saved leads). However, it doesn't specify the exact scope (e.g., all leads vs. filtered) beyond the list context.

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 includes a prerequisite ('requires Sales Navigator subscription'), which provides some usage context. However, it doesn't explicitly state when to use this tool versus alternatives like 'get_saved_leads' or 'sales_search_leads', nor does it mention any exclusions or complementary tools. The guidance is implied rather than explicit.

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