Multilead Open API MCP Server

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

With no annotations provided, the description carries the full burden. It discloses that this is a creation operation ('creates a lead source') and mentions the outcome ('connects it to a campaign for automatic lead import'), but lacks details on permissions, side effects, error handling, or rate limits. It's adequate but not comprehensive.

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?

Well-structured with purpose statement, parameter explanations, return info, and an example. The description is appropriately sized but could be slightly more concise by integrating the example more tightly. Every sentence adds value.

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 tool's complexity (8 parameters, creation operation) and no annotations, the description does well: clear purpose, detailed params, return info, and example. With an output schema present, it doesn't need to explain return values. Minor gaps in behavioral transparency keep it from a 5.

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%, so the description must compensate fully. It provides detailed explanations for all 8 parameters, including examples ('e.g., LinkedIn Sales Navigator search'), optional flags, and default behaviors. This adds significant value beyond the bare schema.

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 tool's purpose: 'Create a lead source and link it to a campaign' with specific examples ('Sales Navigator search URL') and explains the outcome ('automatic lead import'). It distinguishes from sibling tools like 'create_lead' by focusing on lead source creation rather than lead creation.

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 context ('for automatic lead import') but doesn't explicitly state when to use this tool versus alternatives like 'add_leads_to_campaign' or 'create_lead'. It mentions linking to a campaign but doesn't specify prerequisites or exclusions.

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