Sincronizar con MercadoLibre

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

The description adds behavioral context beyond the annotations: it warns that the operation 'Puede tardar' and clarifies that it forcibly syncs against an external API. It does not contradict the annotations, and readOnlyHint=false already signals mutation. A small gap is that it doesn't describe what happens to existing data if sync fails or partially completes.

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 compact and well-structured: the core action comes first, followed by a relevant latency warning, then a clear usage condition. Every sentence earns its place without redundancy.

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 zero-parameter manual sync action, the description is complete: it specifies the data domains synced, warns about duration, and provides a concrete invocation criterion. No output schema exists, but the agent has enough information to decide when and how to call the 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?

There are zero parameters and schema description coverage is 100%, so the schema carries no parameter burden. Per the baseline for 0-param tools, this is a 4; the description doesn't need to explain parameter meanings.

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 states a specific verb ('Fuerza una sincronización') and a clear resource scope ('órdenes, publicaciones y preguntas contra la API de MercadoLibre'). It also distinguishes this tool from the many query/update siblings by emphasizing it forces a sync rather than reading or editing specific data.

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?

Explicit usage guidance is provided: 'Usar solo si el usuario dice que faltan datos recientes; el sistema ya sincroniza solo.' This tells the agent exactly when to invoke the tool and implies the alternative (automatic synchronization) that should be preferred in normal circumstances.

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