Conekta 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. It only states the basic action ('Get a customer by ID') without mentioning permissions, rate limits, error handling, or what the output contains. This is insufficient for a tool that likely involves sensitive customer data.

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 front-loaded with the core purpose in the first sentence, followed by parameter details in a clear 'Args:' section. It's efficient with no wasted words, though the structure is simple and could be more polished.

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 has an output schema (which handles return values) and only one parameter with good semantic coverage in the description, it's minimally adequate. However, the lack of annotations and usage guidelines leaves gaps in understanding behavioral aspects and context.

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 description adds meaningful context for the single parameter: it explains that 'customer_id' is a 'Conekta customer ID' and provides an example format ('cus_2tXyF9BwPG14UMkAA'). Since schema description coverage is 0%, this compensates well, though it could note if the ID is required or sourced from other tools.

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: 'Get a customer by ID.' It specifies the verb ('Get') and resource ('customer'), making it easy to understand. However, it doesn't differentiate from siblings like 'list_customers' or 'create_customer', which is why it's not a 5.

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 siblings like 'list_customers' for multiple customers or 'create_customer' for new ones, nor does it specify prerequisites or exclusions, leaving usage context unclear.

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