Assemble the grocery order

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

The annotation readOnlyHint is true, indicating no side effects, but the description explicitly says 'Drive the browser to fill the cart', which is a mutating action (interacting with the cart). This directly contradicts the read-only annotation, making the behavior unclear and potentially misleading.

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, somewhat run-on sentence that packs in multiple pieces of information (shopping list, browser action, approval, subsequent call). It is not overly long but could be more concise by separating the list generation from the browser actions.

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 provides a multi-step workflow including the need to stop for approval and call another tool, which gives context that might be missing otherwise. However, it does not describe any return value or how the output is structured, and the contradiction about read-only behavior creates uncertainty about the tool's full effect.

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 only parameter, week_id, is a string with no schema description. The text mentions 'selected recipes' and 'preferred store' but does not explain how week_id relates to these, leaving the parameter's purpose ambiguous. The description does not compensate for the lack of schema detail.

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 assembles a shopping list and fills the cart in the browser, which is a specific action. It distinguishes itself from other tools by focusing on the order assembly process, though the mention of calling record_grocery_order adds some complexity.

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 implies usage by referencing 'selected recipes' and 'preferred store', but it does not explicitly state when to use this tool versus alternatives. The instruction to stop before checkout and call another tool provides some guidance, but it lacks a clear condition for invocation.

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