meli_create_item

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the description owes context about consequences — which it omits entirely (no notion of irreversibility, no auth/permission notes, no failure modes). It adds one useful behavioral fact: the payload shape is dictated dynamically by the category, but says nothing about the catalog_confirmed flag, which materially changes what the call does.

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 tight sentences, front-loaded with the action; nothing is wasted. However, the brevity here comes at the cost of omitting essential detail rather than from disciplined editing.

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 high-risk write tool with a free-form nested object, no output schema and 0% parameter documentation, the description is thinner than the complexity demands. It does communicate the one non-obvious concept (category-driven required fields), but omits the catalog_confirmed semantics and the typical preceding lookup step.

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 0% and 'data' is a free-form nested object with additionalProperties:true, so the description is the only source of shape information. It correctly signals that required fields come from the category rather than from the schema, but leaves catalog_confirmed completely undefined and gives no example of the payload.

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?

States a specific verb and resource: 'Crea una publicación' (creates a listing). An agent can tell this is the creation counterpart to meli_update_item / meli_get_item. It stops short of naming any sibling or clarifying scope (e.g. catalog vs. traditional listing) explicitly.

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?

No explicit when-to-use / when-not-to-use guidance and no named alternatives among the many siblings (meli_update_item, meli_search_catalog, meli_catalog_eligibility). The phrase 'campos exigidos por la categoría' only implies that a category lookup (meli_category) should precede the call, without saying so.

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