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 of behavioral disclosure but only states the basic operation and destinations. It fails to address critical integration behaviors such as whether exports are additive or destructive, authentication requirements for HubSpot/Pipedrive/Google Sheets, or whether the operation is synchronous.

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 consists of two efficient sentences with the primary action front-loaded, and every clause provides necessary information about functionality or parameters. There is no redundant or wasted text, making it appropriately sized for the tool's complexity.

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?

The description covers all input parameters and destination options, providing a baseline understanding of the tool's inputs. However, given the external integrations involved and lack of output schema, it has significant gaps regarding return values, error handling, authentication requirements, and the specific behavior of the export operation (e.g., create vs. update).

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?

Given 0% schema description coverage, the description successfully identifies all three parameters by mentioning the destination targets (mapping to the enum values), lead IDs, and minimum score filtering. While it maps the parameters conceptually, it lacks deeper semantic details such as the format of lead IDs, the valid range for scores, or whether filters can be combined.

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 action ('Export leads') and enumerates the five specific destination platforms/formats, providing clear scope. While it differentiates from siblings like lead_ingest or lead_search through its specific destination list, it does not explicitly contrast with them or clarify when to choose this over lead_batch_ingest.

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 mentions the optional filtering capabilities ('Optionally filter by lead IDs or minimum score'), providing implied context for when to use specific parameters. However, it lacks explicit guidance on when to use this tool versus alternatives, prerequisites for external integrations (like authentication), or exclusion criteria.

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