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. It mentions 'tracking and management' but doesn't specify whether this is a read-only or write operation, what permissions are required, if it's rate-limited, or what happens after event creation (e.g., storage, notifications). For a tool with no annotations and potential data mutation, this is a significant gap in transparency.

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 phrase: 'Custom event tracking and behavioral data management'. It's appropriately sized and front-loaded, with no wasted words. However, it could be slightly more structured by explicitly stating the primary action (e.g., 'Create and manage custom events').

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 (4 parameters including nested objects, no output schema, and no annotations), the description is incomplete. It doesn't explain what the tool returns, how events are stored or used, or any prerequisites. For a tool that likely involves data creation and management, more context is needed to guide effective use by an AI agent.

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 100% description coverage, with clear documentation for all 4 parameters (operation, email, eventName, eventData). The description adds no additional meaning beyond the schema, such as explaining the purpose of 'eventData' or constraints on 'eventName'. Since schema coverage is high, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 'Custom event tracking and behavioral data management' states what the tool does at a high level but lacks specificity about the exact operation. It mentions tracking and management but doesn't specify the verb (e.g., 'create' or 'log') or distinguish this from sibling tools like 'campaigns' or 'email_with_tracking' that might also involve event-related operations. The purpose is clear but vague about implementation details.

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. With many sibling tools (e.g., 'campaigns', 'email_with_tracking', 'webhooks'), there's no indication of whether this is for user behavior tracking, system events, or other purposes. It lacks explicit when/when-not instructions or named alternatives, leaving usage context implied at best.

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