leadpipe-mcp

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

With no annotations provided, the description carries the full burden. It successfully discloses duplicate handling ('skipped (duplicates)') and return value structure ('count of ingested and skipped'), but fails to address idempotency, atomicity of batch operations, partial failure behavior, or authentication requirements.

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 extremely compact with zero redundant words. Both sentences deliver essential information (operation type + batch limits, and return value semantics). However, given the tool's complexity, this brevity borders on under-specification rather than optimal conciseness.

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?

For a mutation tool handling complex nested objects with zero schema descriptions, no annotations, and no output schema, the description is insufficient. It lacks documentation of the lead object structure, validation rules, field semantics, and detailed error scenarios that would be necessary for correct agent invocation.

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 0%, requiring the description to compensate for the complex nested lead objects (10+ fields including required 'email', enum 'source', etc.). The description only mentions the batch size constraint ('1-100') but completely omits what constitutes a valid lead object, required fields, or the available data attributes.

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 clearly states the core action ('Add multiple leads') and scope ('at once (1-100)'), distinguishing it from the singular 'lead_ingest' sibling through the batch size specification. However, it does not explicitly name the sibling alternative or clarify when batching is preferred over single ingestion.

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 implies usage constraints through the '1-100' range and hints at behavior with 'Returns count...', but provides no explicit guidance on when to use this tool versus 'lead_ingest', nor does it mention prerequisites, rate limits, or error handling strategies.

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