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 but provides minimal information. It mentions 'send transactional SMS' and 'manage SMS contacts' but doesn't describe what 'manage' means operationally, what permissions are required, whether there are rate limits, cost implications, or what happens when operations fail. For a tool with 16 parameters and no annotation coverage, this is inadequate behavioral 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 extremely concise at just 8 words, which is efficient for such a brief statement. However, it's arguably too brief given the tool's complexity with 16 parameters. While there's no wasted language, the description may be under-specified rather than appropriately concise for a multi-operation tool.

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 (16 parameters, multiple operations via the 'operation' enum), lack of annotations, and absence of an output schema, the description is insufficiently complete. It doesn't explain the relationship between different operations, what each operation returns, error conditions, or how this tool fits within the broader context of sibling communication tools. For a multi-function tool with significant parameter complexity, more contextual information 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?

The schema description coverage is 100%, so all parameters are documented in the schema itself. The description adds no additional parameter semantics beyond what's already in the schema - it doesn't explain parameter relationships, dependencies, or provide usage examples. With complete schema coverage, the baseline score of 3 is appropriate since the description doesn't add value beyond the structured 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 states 'SMS operations - send transactional SMS, manage SMS contacts' which provides a general purpose but lacks specificity. It mentions 'send transactional SMS' and 'manage SMS contacts' but doesn't clarify what 'manage' entails or how this differs from sibling tools like 'contacts' or 'conversations'. The purpose is somewhat vague without clear differentiation from related tools.

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 sibling tools like 'contacts', 'conversations', and 'whatsapp' available, there's no indication of when SMS operations are appropriate versus other communication channels or contact management approaches. The description offers no usage context, prerequisites, or exclusions.

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