Brevo MCP Server

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

With no annotations provided, the description carries full burden but reveals little about behavioral traits. It mentions 'management' which implies mutations, but doesn't specify authentication requirements, rate limits, side effects, or what happens during operations like delete_sub_account. This is inadequate for a tool with 7 parameters and multiple mutation operations.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded with the core functionality.

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 (7 parameters, multiple operations including mutations), lack of annotations, and no output schema, the description is insufficient. It doesn't explain return values, error conditions, or provide enough context for the agent to understand the full scope of enterprise operations beyond the basic domain statement.

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 fully documents all parameters. The description adds no parameter-specific information beyond the high-level domain context. This meets the baseline of 3 since the schema does the heavy lifting, but the description doesn't compensate with additional semantic context.

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 as 'Multi-tenant account and user management for enterprise features', which specifies the domain (enterprise features) and resources (accounts, users). It distinguishes from siblings like 'account' by emphasizing multi-tenancy and enterprise scope. However, it doesn't explicitly mention the specific operations listed in the schema.

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 prerequisites, permissions needed, or differentiate from sibling tools like 'account' or 'crm'. The agent must infer usage from the operation parameter alone.

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