meli_get_order

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered elsewhere. The description adds nothing beyond that: no mention of auth requirements, rate limits, error behavior for invalid IDs, or what an 'order' includes.

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 single short sentence contains no waste and is trivially front-loaded, but its brevity is under-specification rather than efficiency — there is nothing to structure because nothing is said.

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 simple one-parameter read tool the annotations cover safety, and the absence of an output schema means return values need not be explained. However, the order_id format and the distinction from meli_search_orders are missing, which are the two things an agent actually needs to call this 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 0%, so the single order_id parameter is undocumented everywhere. The description does not state the expected ID format, whether it is a Meli order ID or an external reference, or any constraint, leaving the agent to guess.

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 "Obtiene una orden de venta" restates the tool name meli_get_order almost verbatim, adding only that the order is a sales order. It gives no differentiation from the sibling meli_search_orders, which an agent could easily confuse with this one.

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?

There is no guidance on when to use this tool versus alternatives. With meli_search_orders and meli_get_shipment in the sibling set, the agent is left to infer that this fetches a single order by ID rather than searching.

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