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 full burden. It discloses key behavioral traits: the campaign is 'URL-based,' created 'from the user's saved sequences,' and 'goes live immediately after creation.' This covers creation method, timing, and resource dependency, though it lacks details on permissions, error handling, or rate limits.

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 well-structured and front-loaded: the first sentence states the purpose, followed by behavioral details, then a parameter breakdown, return info, and an example. Every sentence earns its place without redundancy, making it efficient and easy to parse.

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 no annotations, 0% schema coverage, and an output schema present, the description does well: it explains purpose, behavior, and parameters thoroughly. However, it could improve by mentioning authentication needs or potential side effects, but the output schema reduces the need for return value details.

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. It provides clear semantics for all parameters: 'user_id' and 'account_id' specify ownership, 'sequence_template_id' identifies the template, 'campaign_name' names the campaign, and 'lead_source_url' is optional for attaching a URL. This adds substantial 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 specific action ('Create a new campaign'), the resource ('from a saved sequence template'), and the type ('URL-based campaign'). It distinguishes this tool from sibling tools like 'create_lead' or 'create_lead_source' by focusing on campaign creation from templates.

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 by mentioning 'saved sequences' and 'goes live immediately,' but doesn't explicitly state when to use this tool versus alternatives like 'create_campaign' (if it existed) or 'add_leads_to_campaign.' No exclusions or prerequisites are provided.

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