get_pantry

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

With no annotations, the description carries the burden. It clarifies that pantry items are excluded from shopping lists, a behavioral trait. It doesn't mention permissions, side effects, or return format details beyond 'list of pantry item names,' which is adequate for this simple tool but not richly transparent.

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?

Two sentences, no wasted words. Front-loaded with the core purpose, then use case and return info. Every sentence earns its place.

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 no output schema and zero parameters, the description is complete: it states what the tool does, when to use it, and what it returns. No additional information is needed for this simple list tool.

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?

There are no parameters (schema coverage 100%), so the description has no burden to add parameter meaning. Baseline is 4 per instructions, and the description doesn't attempt to add anything beyond, which is appropriate.

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 'List pantry items' with a specific verb and resource. It distinguishes from siblings by noting 'excluded from shopping lists' and provides context for use before generating a shopping list, differentiating it from sibling tools like generate_shopping_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 includes 'USE WHEN: checking what's already stocked before generating a shopping list,' providing explicit context for when to use the tool. However, it does not explicitly name alternatives or when not to use it, so it's slightly below the top tier.

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