Armar lista de compra

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

No annotations are provided, so the description carries the full burden. It discloses key behaviors: selection logic, returns per item (chosen product, alternatives, savings, total), handling of budget overflow, and the role of frequentCards. It could be more explicit about non-destructive nature, but overall is transparent.

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 relatively long but well-organized: it starts with the core functionality, then explains parameter behaviors in a logical order. Each sentence adds value, though minor redundancy could be trimmed.

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 7 parameters and no output schema, the description comprehensively covers all key aspects: item conversion, pricing, offers, stock, budget handling, frequent products, and branch-specific prices. It provides enough detail for an AI agent to invoke the tool correctly.

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?

All 7 parameters have descriptions in the schema (100% coverage). The description adds useful context beyond the schema, such as how frequentCards are used and how maxBudget triggers downgrades. This supplements the schema well.

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 it converts a natural language list into concrete products from the catalog, selecting by best price per unit and offers. This distinguishes it from sibling tools like search_products or get_offers, which have different scopes.

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?

The description provides clear usage context, such as using branchId for local prices and frequentCards to prioritize frequent purchases. It does not explicitly list when not to use the tool or alternatives among siblings, but the guidance is sufficient for typical scenarios.

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