Genera un link de pago de MercadoPago para comprar un Brand Book Profesional ($310.000 ARS). Requiere audit_id de brand_audit + datos de contacto.
| Name | Required | Description | Default |
|---|---|---|---|
| audit_id | Yes | ID del audit | |
| contact_name | Yes | Nombre completo del comprador | |
| contact_email | Yes | Email del comprador | |
| referral_code | No | Código de referido (10% descuento) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavior. It correctly reveals that the tool generates a payment link (not a charge) and requires audit_id and contact data. However, it does not mention side effects like creating an order or link expiration, leaving some behavioral gaps.
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, focused sentence that delivers the core purpose, price, and prerequisite. It is concise, front-loaded, and contains zero 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?
For a transactional tool with four parameters and no output schema, the description captures the essential context: what it does, the price, and required inputs. A minor gap is not explaining that the payment link is likely used for an immediate purchase flow, but the overall context is sufficient.
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 coverage is 100% with each parameter described, so the baseline is 3. The description adds value by relating audit_id to brand_audit, clarifying the expected input source beyond the schema's generic 'ID del audit'.
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 function with a specific verb ('Genera un link de pago de MercadoPago') and a specific resource ('Brand Book Profesional' at a set price). This unambiguously distinguishes it from sibling tools like brand_audit or generate_proposal.
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 a clear prerequisite: 'Requiere audit_id de brand_audit + datos de contacto,' indicating the proper context after completing a brand audit. It does not explicitly mention alternatives, but the unique purpose makes the usage intent clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct stage of the branding workflow: audit, status, viewing details, proposal, purchase, and catalog. The only potential overlap is between brand_book_status and brand_book_viewer, but their descriptions clearly distinguish progress tracking from full content access.
Tools use snake_case throughout with a mostly predictable pattern, but there is a mix of noun_noun (brand_audit, brand_book_status) and verb_noun (generate_proposal, purchase_brand_book) forms. The style is consistent and readable, though not uniformly verb-first.
Six tools is well-scoped for a niche branding service, covering discovery, sales, and delivery without redundancy or bloat. Each tool earns its place in the workflow.
The core journey from audit to proposal to purchase to accessing the brand book is fully covered, with the visual catalog as a useful resource. Minor gaps like a list-all-brand-books tool or an update tool exist, but they are likely handled outside the agent's scope.