Search paginated sales orders for a seller to review transactions and manage order workflows.
Busca órdenes de venta de un vendedor paginadas.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | date_desc | |
| limit | No | ||
| offset | No | ||
| seller_id | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds only that results are paginated — useful, but it omits the maximum page size, default ordering behavior, rate limits and what an empty result means.
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?
A single short sentence with no filler and the scope (seller) front-loaded. It is efficiently written, though efficiency here comes at the cost of substance rather than from trimming 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?
With four parameters, 0% schema description coverage and no output schema, the description should explain pagination mechanics and sorting options; it does neither. An agent can guess how to call it but cannot call it well, e.g. it has no idea of a safe limit or valid sort keys.
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 description must carry parameter meaning and it does not: sort, limit, offset and seller_id have no documented accepted values, ranges or defaults beyond the bare schema titles. Only the phrase 'de un vendedor' loosely implies seller_id's role, and 'paginadas' loosely implies limit/offset.
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 (search a seller's sales orders) plus the pagination nature of the result. It implicitly separates itself from meli_get_order (single order lookup) but never names that sibling 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 when-to-use guidance at all: nothing tells the agent to prefer this over meli_get_order for a known order id, nor when pagination is appropriate. The word 'paginadas' hints at bulk listing but no conditions or alternatives are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.