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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only 'filtered and paged', which hints at pagination but doesn't explain the default page size, how cursor continuation works, or what a row contains — and there is no output schema to fall back on.

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?

A single sentence with zero filler, front-loaded on the resource and immediately followed by the scope and capabilities. Nothing is repeated or wasted.

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 five-parameter read tool with no output schema, the description is thin: it doesn't characterize the returned records (e.g., quantity, freshness, group labels) or how paging terminates. The annotations cover safety and the schema covers parameters, but return-shape context is absent.

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 100% and enums document group and place values thoroughly, so the schema carries the parameter burden. The description's 'filtered and paged' only loosely maps to query/cursor and adds no syntax or semantics beyond the 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?

A clear verb-plus-resource statement ('Read what the household has at home: pantry, fridge and freezer') that scopes the resource to all three storage locations. It implicitly excludes the shopping list and meal plan siblings, though it never names them explicitly.

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 by 'what the household has at home', so it's clear this is the read path for stored food. However, it never says when to prefer this over get_household_overview or get_shopping_list, nor when to omit filters versus use them.

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