Purchase insights and smart basket

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

Annotations declare readOnlyHint=true. The description adds important context: it renders an interactive view and does not add anything to cart without explicit user approval. This clarifies it is non-destructive and reveals the interactive behavior beyond the annotation.

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?

Two sentences: the first states the core analysis capabilities, the second explains interactive behavior and safety. No redundant information, front-loaded with purpose.

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?

The description lists key output sections (frequent products, spend by month/category, images, suggestions) and mentions interactive rendering. While no output schema exists, this gives a solid understanding of returns. Lacks detail on error handling or edge cases, but sufficient for the tool's complexity.

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 coverage is 100% with existing parameter descriptions. The description adds context for include_offline ('optional cached offline tickets') and suggestion_mode ('backtested repeat-purchase suggestions') but does not significantly enhance meaning beyond the schema. Baseline of 3 is appropriate.

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 analyzes full online order history and offline tickets to provide frequent products, spend breakdowns, images, and purchase suggestions. This distinguishes it from sibling tools like get_purchase_history or add_to_cart, which focus on raw data or cart actions.

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 explicit guidance on when to use this tool versus alternatives such as get_purchase_history for raw data or get_shopping_guide for recommendations. The description implies it is for aggregated insights but lacks when-not-to-use or alternative tool references.

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