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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is known. The description adds nothing beyond that—it does not say whether the tool organizes, validates, sorts by aisle, or outputs an aggregated list, which is important context for a 'planner'.

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?

Three words are technically concise, but this is under-specification rather than useful brevity. There is no front-loaded scope or key constraint to orient the agent.

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?

For a tool that requires a structured array of grocery items, the definition is missing any description of input format, behavior, or expected output. It relies entirely on the schema and annotations, which together do not explain the tool's planning behavior.

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%, so the description must compensate, but it does not. It omits any explanation of the required items array or the nested name, qty, unit, and aisle fields, leaving the parameter's expected format and semantics undocumented.

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?

"Grocery list planner" essentially restates the tool name and title rather than stating a concrete verb and resource. An agent cannot tell what the tool actually does with the provided items or how it differs from siblings like planning_packing_list.

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 gives no indication of when to use this tool, when not to, or which sibling tools it might replace. The relationship to planning_packing_list, planning_inventory, or scale_recipe is entirely unaddressed.

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