ManyContacts MCP Server

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

No annotations are provided, so the description carries full burden. It mentions statistics but doesn't disclose behavioral traits such as pagination, rate limits, authentication requirements, or whether the list is real-time or cached. For a listing tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves operationally.

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 a single, efficient sentence that front-loads the core action ('List WhatsApp Business bulk messaging campaigns') and adds valuable context ('with statistics...'). There's zero waste, and every word earns its place by clarifying scope and output characteristics.

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 (listing with statistics), lack of annotations, and no output schema, the description is minimally adequate. It specifies the resource type and statistics included, but doesn't cover return format, error handling, or operational constraints. For a tool with no structured metadata, more behavioral context would be beneficial.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate. Baseline is 4 for 0 parameters, as the description correctly focuses on purpose rather than unnecessary parameter explanations.

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 verb ('List') and resource ('WhatsApp Business bulk messaging campaigns'), specifying the exact scope of what's returned. It distinguishes from sibling tools like manycontacts_campaigns_create and manycontacts_campaigns_delete by focusing on listing with statistics rather than creating or deleting campaigns.

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 'with statistics (sent, delivered, read, failed counts)', suggesting this tool is for retrieving campaign performance data. However, it doesn't explicitly state when to use this versus alternatives like manycontacts_funnels_list or manycontacts_messages_list, nor does it provide exclusions or prerequisites.

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