search-cellar

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

Annotations provide readOnlyHint and openWorldHint. Description adds valuable behavioral context: returns up to 25 results per page, pagination via offset, and region searches across multiple fields. This goes beyond what annotations alone convey.

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. First sentence states purpose, second adds pagination details. Front-loaded with key information.

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?

With 8 parameters and an output schema, the description covers search scope, pagination, and region behavior. No mention of ordering or default sort, but sufficient for most users given the output schema presumably provides that.

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 coverage is 100% with descriptions, but the description adds specific meaning: region searches across Country, Region, SubRegion, Appellation, and Locale fields. This enriches the schema's 'Region, country, or appellation' description.

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?

Description clearly states 'Search your wine cellar' with specific verb and resource, and lists multiple searchable criteria (name, color, region, etc.). It distinguishes from siblings by focusing on search with multiple filters, unlike other tools like get-wishlist or drinking-recommendations.

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 for searching with filters and pagination, but does not explicitly state when to use this tool versus alternatives like bottle-details or drinking-recommendations. No when-not-to-use guidance is provided.

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