get_invoices

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

Without annotations, the description must cover behavioral traits. It does not mention read-only nature, authentication needs, rate limits, or side effects. The minimal description fails to disclose whether the operation is safe or what happens with different parameter combinations.

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 a single sentence with no fluff, but it is too brief to be effective. It sacrifices essential details for brevity, making it merely adequate rather than exemplary.

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?

Given the presence of an output schema and three parameters, the description is incomplete. It does not explain how parameters interact (e.g., whether both 'order_id' and 'days_back' can be used together) or what the output represents, leaving gaps for a complete understanding.

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 adds no meaning to the parameters. It does not explain the role of 'order_id', 'days_back', or 'marketplace', leaving the agent to infer from names and defaults alone.

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 the tool's purpose: obtaining invoices by order or period. It uses a specific verb ('obtener') and identifies the resource ('facturas'), with filtering criteria that distinguish it from siblings like 'download_invoice' (download action) and 'get_order_finances' (different resource).

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 usage guidance is provided. The description lacks information on when to use this tool versus alternatives (e.g., 'download_invoice' for PDFs) and offers no exclusions or prerequisites.

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