Smartlead: list campaigns

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

Beyond annotations (readOnlyHint, destructiveHint), the description explicitly states 'may consume SmartProspect credits: no; creates or modifies remote state: no; can send email: no; destructive: no' and 'Free and read-only'. This adds detailed safety context, and there is no contradiction with 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 concise and well-structured: one sentence for purpose, one for safety, one for endpoint, and a short concluding phrase. Every sentence adds distinct value with no redundancy except minor repetition of 'read-only'.

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 an output schema exists, return values are covered. The description plus annotations and schema fully cover the behavior of this simple list tool: what it does, safety profile, endpoint, and parameter details. No critical gaps remain.

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 description coverage is 100%, with both parameters (client_id, include_tags) already described in the input schema. The tool description does not add additional parameter semantics, so the baseline of 3 applies.

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 opens with 'List all Smartlead campaigns with status, schedule and sending configuration', which is a specific verb ('List'), resource ('Smartlead campaigns'), and scope ('all'). This clearly distinguishes it from sibling tools like smartlead_get_campaign which fetches a single campaign.

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 clearly implies usage for listing all campaigns, but it does not explicitly mention alternatives or when-not-to-use. The 'List all' phrasing provides clear context and filters, though no exclusions or alternatives are stated.

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