leadpipe-mcp

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

No annotations provided, so description carries full burden. Discloses duplicate rejection policy ('Duplicate emails are rejected'), but omits other critical mutation behaviors: success response format, whether operation is atomic, idempotency guarantees, or error handling beyond duplicates.

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?

Two sentences with zero redundancy. First sentence establishes action and target; second covers required fields, examples, and key constraint. Front-loaded with critical information (duplicate rejection).

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 11 parameters with nested objects and no output schema, description covers the critical path (email requirement, duplicate handling) but leaves significant gaps. No explanation of custom_fields structure, source enumeration, or return value.

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 has 0% description coverage. Description compensates partially by identifying email as required and listing example optional fields (name, job title, company), but fails to explain 7 other parameters including complex nested 'custom_fields' object, 'tags' array, or 'source' enum values.

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?

States specific action ('Add') and resource ('new lead') with scope ('to the pipeline'). Singular 'lead' clearly distinguishes from sibling lead_batch_ingest, and 'Add' differentiates from lead_search or lead_export.

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?

Identifies required vs optional fields ('email (required) and optional fields'), implying basic usage pattern. However, lacks explicit guidance on when to use lead_batch_ingest instead, or prerequisites like authentication needs.

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