Criar cobrança SPEI (México)

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

Annotations indicate a write operation (readOnlyHint=false) and the description confirms it creates a charge and returns a CLABE. It adds the XPAG minimum caveat for the 'valor' parameter, but could further disclose synchronous behavior or post-creation steps.

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?

Three concise sentences front-load the core purpose and output, then quickly cover requirements and document details with no redundant information.

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 simple parameter structure and no output schema, the description adequately covers creation, output, and requirements. It could mention how to use the returned CLABE, but overall is fairly complete for a straightforward creation tool.

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?

With 100% schema description coverage, the baseline is 3. The description adds minor semantic value by clarifying document types (RFC or CURP) and the XPAG minimum for 'valor', but largely reiterates schema information.

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 action ('Cria uma cobrança SPEI'), the currency (MXN), and the output (18-digit CLABE), distinguishing it from siblings like createPixCharge or createPayPalOrder which target other payment systems.

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 specifies prerequisites ('Requer conta ZuckPay com SPEI habilitado') and acceptable documents (RFC or CURP), but does not explicitly direct when to use this tool versus alternatives, although the sibling list provides implicit context.

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