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 offers minimal behavioral insight. It mentions 'integration' but doesn't disclose whether operations are read-only, destructive, require authentication, have rate limits, or what the response format might be. For a tool with 23 possible operations including deletions and updates, this lack of transparency 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 a single, efficient sentence that lists key domains without unnecessary words. It's appropriately sized for a high-level overview, though it could be more front-loaded with a clearer verb. Every word earns its place by outlining scope.

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 (12 parameters, 23 operations, no output schema, no annotations), the description is incomplete. It doesn't address behavioral traits, usage context, or output expectations. For a multi-operation tool handling sensitive e-commerce data, more guidance is needed to help the agent use it 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?

Schema description coverage is 100%, so the schema documents all 12 parameters thoroughly. The description adds no parameter-specific information beyond the high-level domains mentioned. It doesn't explain how parameters like 'operation' interact with others or provide examples. Baseline 3 is appropriate since 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 the tool manages orders, products, coupons, and payments, which gives a general purpose but is vague about the specific actions. It doesn't distinguish from sibling tools like 'account' or 'crm' that might overlap in business domains. The description lacks a specific verb beyond 'manage' and doesn't clarify if this is for integration, API calls, or internal operations.

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?

No guidance is provided on when to use this tool versus alternatives. The description lists domains (orders, products, etc.) but doesn't specify context, prerequisites, or exclusions. Given sibling tools like 'campaigns' or 'crm' that might handle related e-commerce functions, the agent has no help in choosing between them.

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