Smartlead: get campaign leads

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

Beyond the annotations' readOnlyHint and destructiveHint, the description explicitly enumerates safety properties: 'may consume SmartProspect credits: no; creates or modifies remote state: no; can send email: no; destructive: no.' It also adds a privacy note about returning personal data (emails and names), which is valuable context not present in 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 remarkably concise, with a single-sentence purpose followed by a compact safety/endpoint block. Every sentence carries meaningful information; there is no redundancy or filler.

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 an output schema present (per context signals) and full parameter documentation in the input schema, the description only needs to convey safety and data sensitivity, which it does. It also specifies the REST endpoint, providing a complete operational picture.

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% with detailed descriptions for each parameter. The description's mention of 'pagination and status/engagement filters' adds no new meaning beyond the schema, so it earns the baseline score for a well-documented schema.

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 'List leads in a campaign with pagination and status/engagement filters,' which is a specific verb+resource combination that clearly distinguishes this tool from siblings like smartlead_get_campaign (which retrieves campaign details) and smartlead_get_campaign_analytics (which returns analytics). The scope is unambiguous.

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 does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisite conditions. It simply describes the function without situating it among the many sibling tools.

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