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. 'Process' implies some action but doesn't specify whether this is read-only, mutative, or has side effects. It doesn't mention authentication needs, rate limits, error conditions, or what the tool returns. The description is too generic to provide meaningful behavioral context for a tool with 8 parameters.

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 5 words with no wasted language. However, this brevity comes at the cost of being under-specified for a tool with significant complexity (8 parameters, multiple operations). While front-loaded, it lacks the necessary detail to be truly helpful.

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?

For a tool with 8 parameters, multiple distinct operations via an enum, no annotations, and no output schema, the description is inadequate. It doesn't explain the different operation types, when to use each, what the tool returns, or how it differs from sibling tools. The minimal description fails to provide the context needed for effective tool selection and use.

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 8 parameters thoroughly with descriptions, enums, defaults, and requirements. The description adds no parameter-specific information beyond the generic 'process inbound emails and attachments' statement. With complete schema coverage, the baseline score of 3 is appropriate.

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 'Process inbound emails and attachments' states a general purpose but is vague about what 'process' entails. It mentions the resource (inbound emails and attachments) but lacks specificity about the actual operations available (listing, retrieving, downloading). The description doesn't distinguish this tool from potential email-related siblings like 'email' or 'conversations'.

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 siblings like 'email' and 'conversations' that might handle email-related functions, there's no indication of when this inbound processing tool is appropriate versus those other tools. No context, exclusions, or prerequisites are mentioned.

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