Conectar una tienda de MercadoLibre

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

Annotations already convey readOnlyHint, openWorldHint, and non-destructive behavior. The description adds meaningful context by stating it 'Devuelve un link que el usuario abre en el navegador' and explicitly declaring 'no autoriza nada por su cuenta,' which clarifies the side-effect boundary beyond what annotations provide.

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 three concise sentences with the core function first, then explicit usage triggers, then a clarifying behavioral note. Every sentence earns its place and the most decision-relevant information is front-loaded.

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 one optional boolean parameter and no output schema, the description covers what the tool does, when to use it, what it returns, and what it does not do. An agent has enough information to select and invoke 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%, and the single optional boolean parameter 'diagnostico' is already documented in the schema. The tool description itself adds no further parameter-level meaning, so 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 opens with a specific verb and resource: 'Genera el link de autorizacion para vincular una cuenta de MercadoLibre nueva' and also mentions showing the status of already connected accounts. This clearly separates the tool from siblings like ml_cuentas or ml_sincronizar by focusing on the authorization-link connection flow.

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?

It gives explicit trigger conditions with exact user phrases: 'quiero conectar mi tienda', 'agregar otra cuenta', 'vincular MercadoLibre', plus the fallback scenario 'cuando alguna herramienta falla porque no hay cuentas.' However, it does not name alternative sibling tools or specify when not to use it, so it falls just short of a 5.

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