meli_get_shipment

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 structurally. The description adds nothing beyond that: no mention of auth/scope requirements, response shape, error behavior for unknown IDs, or that the lookup is a live external API call (openWorld).

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?

It is a single short sentence with no filler and the key concept is front-loaded, but the extreme brevity comes at the cost of substance 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?

The tool is simple (one required string param, read-only annotations, no output schema), so it does not need much, but with zero schema descriptions and no output schema the description should at least characterize the identifier or the returned shipment shape. As written, an agent knows only the bare minimum.

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?

With schema description coverage at 0%, the description carries the burden and does little: it says lookup is "por identificador" but never explains the expected format of shipment_id, where a shipment ID comes from, or whether it is the same ID returned by meli_search_orders.

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 and resource ("Obtiene un envío" – get a shipment) plus a lookup key (identifier), so the operation is identifiable. However, it does nothing to distinguish it from siblings that also read order/shipment-like resources (meli_get_order, meli_search_orders), leaving the agent to infer scope from the name alone.

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, no mention of prerequisites or required identifiers, and no exclusions. The only implicit cue is "por identificador," which merely restates the single required parameter.

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