Brevo 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 of behavioral disclosure. It mentions 'analyzes text, maps attributes, checks duplicates, and imports efficiently', which hints at mutation and processing behavior, but fails to specify critical details like required permissions, rate limits, error handling, or what 'efficiently' entails. This is inadequate for a mutation tool with zero annotation coverage.

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 purpose ('Intelligent bulk contact import from pasted text') and lists key actions without waste. Every phrase adds value, making it appropriately concise and well-structured.

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 (bulk import with mutation), lack of annotations, and no output schema, the description is incomplete. It omits essential context such as return values, error conditions, performance expectations, and how it integrates with sibling tools. This leaves significant gaps for an AI agent to understand and invoke the tool correctly.

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 schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds no specific parameter semantics beyond implying 'pasted text' for the 'text' parameter. It doesn't compensate for any gaps, but with high schema coverage, the baseline is 3.

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: 'Intelligent bulk contact import from pasted text' with specific actions like analyzing, mapping, checking duplicates, and importing. It distinguishes from simpler contact tools by emphasizing bulk processing and intelligence, though it doesn't explicitly differentiate from all sibling tools like 'contact_with_list'.

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 provides no guidance on when to use this tool versus alternatives like 'contacts' or 'contact_with_list', nor does it mention prerequisites or exclusions. It implies usage for bulk imports from text but lacks explicit context for tool selection.

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