Smartlead: get lead by email

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description goes beyond this by explicitly stating no SmartProspect credit consumption, no email sending, no remote state modification, and that it returns personal data. It also provides the endpoint. This adds significant behavioral context beyond the structured 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: a single-purpose statement, followed by neatly labeled safety details, and a final note about personal data. Every sentence adds value, and no unnecessary words are used.

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 simple nature of the tool, the presence of an output schema, and the annotations, the description fully covers purpose, safety, endpoint, and a privacy consideration. It is complete for an agent to select and invoke the tool confidently.

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 schema has 100% coverage over the sole 'email' parameter, with its own description 'Email address to look up.' The tool description only reiterates the email-based lookup without adding format, examples, or constraints. Baseline of 3 is correct since the schema does the heavy lifting.

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 a clear, specific verb+resource: "Look up a single lead by email address and return its associated campaign data." This immediately distinguishes it from sibling tools like smartlead_list_campaigns or smartprospect_get_contacts. The scope is precise and 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 clearly implies the use case: looking up a lead by email. It provides context but does not explicitly mention alternatives or when not to use this tool. Since the tool is simple and the context is clear, it does not need exclusions, but naming an alternative would have pushed it to a 5.

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