Smartlead: get campaign analytics

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

Annotations already provide readOnlyHint=true and destructiveHint=false. The description goes beyond this by explicitly stating 'may consume SmartProspect credits: no' and 'can send email: no', adding useful side-effect context. The endpoint is also disclosed, which helps understanding the remote operation.

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 compact, starting with a clear purpose sentence, followed by a structured safety summary and endpoint. Every sentence earns its place; no fluff or repetition.

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 the tool's simple parameter set (one required integer) and the presence of an output schema (so return values need no explanation), the description is fully sufficient. It covers purpose, safety, and endpoint without requiring further clarification.

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 fully documents campaign_id with type integer and description 'Campaign ID' (100% coverage). The description mentions 'one campaign' but does not add extra detail about how to obtain or format the ID, so it provides minimal incremental meaning beyond the 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 a specific verb ('Retrieve') and resource ('performance analytics for one campaign') along with the included metrics (sent, opened, replied, bounced). This clearly distinguishes it from siblings like smartlead_get_campaign, which likely fetches campaign details rather than analytics.

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 when to use this tool: when needing analytics for a specific campaign. The read-only safety guarantees also make it a safe choice for read operations. However, it does not explicitly name alternatives or exclusions, but the single-purpose phrasing provides sufficient context.

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