plan

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

No annotations are provided, so the description carries full burden. It discloses that it does not add to cart, which is a useful behavioral trait, but it doesn't disclose other side effects, whether it reads or writes elsewhere, or what it returns. The tool likely creates a plan (given sibling 'add_plan'), but no side effects are mentioned. This is insufficient transparency.

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 two short sentences, front-loaded with the core action and a key constraint. No filler words; every word contributes. It's appropriately concise.

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 4 parameters, no schema descriptions, no annotations, and no output schema, the description is far too sparse. It doesn't explain parameter meanings, return values, or usage scenarios, leaving the agent to guess. It covers only the most basic purpose.

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?

Input schema has 4 parameters with zero descriptions, and the tool description mentions none of them. 'Items' is inferable as the grocery list, but budget, save_to_file, and summary_only are entirely unexplained. The description adds no parameter semantics over the bare schema.

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 'Parse grocery list, find matches. Does not add to cart.' This names a specific verb (parse/find) and resource (grocery list), with a scoping note ('does not add to cart') that differentiates from cart-modifying sibling tools. However, it doesn't explicitly distinguish from sibling 'search' or 'deals', so it's clear but not fully differentiated.

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?

Usage is implied: it's for parsing a grocery list and finding matches, and it clarifies it won't add to cart. But it doesn't explicitly say when to use this over alternatives like 'search' or 'cart_diff', and doesn't mention conditions or exclusions beyond the cart note. Thus, implicit guidance only.

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