Cuentas conectadas

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, and the description adds useful behavioral detail about the output: linked accounts, app configuration state, active accounts, and webhook status. It does not contradict the annotations and does not imply any hidden side effects.

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?

Two sentences, front-loaded with the purpose and output items, followed by a practical usage note. Every part of the description earns its place; there is no filler or repetition.

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 parameterless read-only listing tool with no output schema, the description is complete: it names the output categories, the connection-state fields, and the canonical use case. An agent has enough information to select and invoke the tool 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?

The tool has zero parameters, so there is little semantic burden on the description. The description even supports parameter selection indirectly by explaining that the tool reveals which account ID to pass in the 'cuenta' parameter of 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 specifies a concrete action ('Lista') and resource ('cuentas de MercadoLibre vinculadas'), and it clarifies what aspects of the connection state are included (app configurada, cuentas activas, webhook). This clearly distinguishes the tool from the many sibling tools that operate on orders, publications, metrics, or messaging.

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 an explicit usage directive: use it at the beginning when there is more than one account, and explains the purpose is to know which ID to pass in the 'cuenta' parameter of other tools. This is direct, actionable guidance that tells the agent when to invoke the tool.

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