list_lead_lists

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

No annotations are provided, so the description carries full burden of behavioral disclosure. It gives no indication of pagination, ordering, whether this is a read-only operation, rate limits, or what the response structure looks like. For a list-with-no-parameters tool, the agent has no idea what to expect back or whether the call is safe/cheap.

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?

A single sentence that is efficient and front-loaded. It states the purpose without waste. However, it could be argued it under-specifies rather than being tautological - it's not padded but it's also minimal.

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?

With a 0-parameter, no-output-schema, no-annotation tool, the description is the only source of information. It tells the agent only what the tool does but not what to expect from the call. For a list operation, there's no note on result format, volume, or filtering capabilities. Given the low complexity, this is a simple tool, but the description still leaves meaningful gaps about the response.

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 tool has 0 parameters, so there's nothing to document. Per the rubric, 0 params earns a baseline of 4. The description correctly omits parameter details because there are none.

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 states the tool lists Hunter.io lead lists associated with the account (verb+resource). It's clear about what it does and it distinguishes from siblings like create_lead_list and sync_lead_list, but the phrase 'associated with the account' adds minimal differentiation from other list-related tools. It's adequate but not exemplary.

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 vs alternatives. The reader must infer from the name that this is for reading/viewing lists, and there are related tools (create_lead_list, sync_lead_list, list_leads) whose relationship to this tool isn't clarified. No exclusions, prerequisites, or alternative tool references.

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