leadpipe-mcp

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

With no annotations, description carries full burden. Adds valuable behavioral context: reveals data source (email domain lookup) and specific enrichment fields. However, omits critical safety traits: unclear if this mutates the lead record or returns data, no mention of rate limits, failure modes, or permissions required.

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, zero waste. First sentence front-loaded with action, mechanism, and deliverables. Second sentence states the single requirement. Every word earns its place.

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?

Adequate for a single-parameter tool: describes the enrichment action and required input. However, given no annotations and no output schema, gaps remain regarding return format, success/failure behavior, and whether the operation is idempotent or destructive.

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 100% description coverage (lead_id documented). Description reinforces this requirement ('Provide the lead ID') but adds no additional semantic depth regarding format, constraints, or sourcing of the ID beyond what the schema already states.

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?

Excellent specificity: verb 'Enrich' + resource 'lead' + exact data fields (industry, size, country, tech stack) + mechanism (using the email domain). Clearly distinguishes from sibling lead_ingest (creation) and lead_score (scoring) by specifying the company data enrichment function.

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?

Implies prerequisite by requiring lead_id ('Provide the lead ID'), suggesting prior ingestion needed, but fails to explicitly name lead_ingest as the prerequisite tool or clarify when to use this single-lead tool versus batch alternatives.

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