Smartlead: list lead lists

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

The description goes beyond the annotations by explicitly stating that it consumes no SmartProspect credits, does not create or modify remote state, cannot send email, and is not destructive. This directly addresses safety and side-effect concerns, adding significant value over the readOnlyHint and destructiveHint annotations.

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 two concise sentences. The first sentence states the core functionality, and the second summarizes safety and endpoint details. No unnecessary words or repetition. Information is front-loaded.

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 simple, read-only list operation with four optional parameters and an output schema, the description is complete. It states the endpoint, confirms read-only behavior, and the output schema covers return values. No critical information is missing.

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 provides 100% coverage with detailed descriptions for all four parameters. The description mentions 'name and tag filtering' which maps to listName and tagIds, but adds no new semantic information beyond summarizing what the schema already states. This meets the baseline for full schema coverage.

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 tool's action ('List') and resource ('saved lead lists'), and mentions the optional filtering capabilities ('name and tag filtering'). This unambiguously distinguishes it from sibling tools like smartlead_list_campaigns or smartlead_list_email_accounts.

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 clear context: this is for listing lead lists, with optional filters. While it does not explicitly name alternatives or exclusion criteria, the purpose is self-evident and aligns with the tool's name. The 'Free and read-only' note adds practical guidance.

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