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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds valuable behavioral context by specifying the content of the listing (pantry, fridge, freezer) and that it includes expiry dates where known. This goes beyond the annotations without contradicting them, though it could also mention the return format more explicitly.

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 sentences with no fluff. The core purpose is front-loaded, and the usage guidance is appended efficiently. Every word earns its place, making it highly scannable for an 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 read-only listing tool with no parameters and no output schema, the description covers what it does, what it returns (with expiry where known), and when to use it. It is adequate for an agent to invoke correctly, though it could specify whether the output is a flat list or grouped by location, which is a minor gap.

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?

With zero parameters, the description does not need to explain parameter semantics. The schema coverage is effectively 100% (no parameters), and the baseline for 0-param tools is 4. The description correctly focuses on the tool's behavior rather than parameters that don't exist.

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 a specific action (list) and resource (kitchen contents including pantry, fridge, freezer), and clearly distinguishes it from sibling tools like add_pantry_items or list_recipes. It also provides concrete use cases such as 'what they have' and 'what is about to go off', making the tool's purpose unambiguous.

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 explicitly states when to use the tool ('Use this when they ask what they have, what is in the fridge, or what is about to go off'), providing clear triggers for invocation. While it does not mention alternatives, the contexts are specific enough to avoid misuse, and the scope is well-defined.

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