create_lead_list

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 does not state whether creating a list is a mutating destructive operation, whether duplicate names are allowed or rejected, rate limits, or what happens on creation. For a create operation with zero annotation coverage, this is a meaningful gap.

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 with zero wasted words. It front-loads the action and resource clearly. However, it could include a bit more behavioral note without becoming verbose, which prevents a 5.

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 mutation tool (create operation) with no annotations and no output schema, this description is thin. It gives no indication of return values, validation behavior, side effects, or relationship to sibling list tools. A more complete description would note that the created list can then be populated via sync_lead_list or used in campaigns.

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 coverage is 100% for the single 'name' parameter, which the schema documents as 'List name (1-200 chars)'. The description adds virtually no parameter-level information beyond what the schema provides. Following the calibration baseline for high schema coverage, a 3 is appropriate.

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 'Create a new Hunter.io lead list' clearly states the action (create) and the resource (lead list). It is specific enough to distinguish the purpose from siblings like list_lead_lists (listing) and sync_lead_list (syncing existing lists). It doesn't specify additional scope or list-creation semantics but is adequate.

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?

There is no guidance on when to use this tool versus alternatives. It doesn't mention that list_lead_lists exists for viewing existing lists, or that create_deal is the sibling for deal creation. The usage context (e.g., create a list first, then use sync_lead_list to populate it) is entirely absent.

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