pedidos_recientes

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

The verb 'Lista' implies a read-only operation, and no destructive behavior is indicated. However, without annotations, the description does not explicitly state that the tool does not modify data, but the intent is clear.

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, using only three short lines to convey purpose and parameter details. No unnecessary words are present, and the docstring format is clean.

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 being concise, the description lacks information about the output format (fields in each order), ordering, or pagination. With no output schema, more detail on return structure would improve completeness.

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?

The description fully explains both parameters: 'horas' as a backward window in hours (default 24) and 'max_pedidos' as maximum orders to return (default 50). Since the input schema has 0% description coverage, the description compensates completely.

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 clearly states 'Lista los pedidos de las últimas N horas' (lists orders of the last N hours), specifying a verb and resource with a time window. It distinguishes from siblings like 'inventario' (inventory) and 'resumen_ventas' (sales summary) by focusing on recent orders.

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. The description does not mention prerequisites, exclusions, or scenarios where sibling tools would be more appropriate.

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