get_orders

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

With no annotations, the description carries full burden. It does not disclose read-only nature, pagination, rate limits, or behavior for empty results. The description only hints at filtering but fails to provide behavioral details necessary for safe invocation.

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 description is extremely concise (7 words), but this brevity sacrifices informativeness. It is front-loaded but lacks substance, leaving critical gaps in understanding. Every sentence must earn its place, but this one feels incomplete.

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?

Despite having an output schema (not provided here), the description does not explain return values, pagination, or the scope of orders. Given that the tool has 3 optional parameters and no enums, the description should cover more context, especially for a generic order retrieval tool.

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 the description only implicitly references 'fecha y estado' (date and status). It does not explain the 'marketplace' or provide formats or allowed values. The description adds minimal meaning beyond the parameter names and defaults.

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 'Pedidos recientes por fecha y estado' which indicates the tool retrieves recent orders filtered by date and status. However, it does not explicitly state the action (e.g., 'list' or 'get'), and it lacks differentiation from sibling tools like get_order_items or get_order_metrics. The purpose is clear but vague.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or context. The description implies it is for filtering orders by date and status, but without explicit usage context, the agent has no direction.

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