Brevo MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description mentions 'handle customer conversations' which implies read and write operations, but doesn't specify authentication requirements, rate limits, side effects, or what happens when operations fail. For a tool with 5 parameters including operations like 'send_message' and 'update_conversation', this lack of behavioral context is a significant gap.

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 brief and to the point with just two phrases separated by a dash. It efficiently communicates the tool's domain without unnecessary words. However, it could be more front-loaded with specific capabilities rather than just general categories.

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 complexity of a multi-operation tool with 5 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the tool returns, how operations differ, or provide any context about the conversation system. For a tool that can perform 5 different operations ranging from reading conversations to sending messages, more comprehensive guidance is needed.

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 100%, so the schema already documents all 5 parameters with descriptions and enums. The description adds no parameter-specific information beyond what's in the schema. It doesn't explain relationships between parameters (e.g., that 'conversationId' is required for certain operations) or provide usage examples. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 states 'Chat and conversation management - handle customer conversations' which provides a general purpose (managing conversations) but lacks specificity. It mentions 'handle customer conversations' which suggests a customer service context, but doesn't specify what operations are available or distinguish this tool from potential sibling tools like 'sms' or 'whatsapp' which might also handle conversations. The purpose is clear at a high level but vague about the specific capabilities.

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. It doesn't mention any prerequisites, constraints, or relationships with sibling tools like 'sms', 'whatsapp', or 'inbound' which might also handle communication. There's no indication of when to choose this conversation tool over other messaging or contact management tools available on the server.

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