Find GenieLocker agent and inference recipes

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

Annotations already declare readOnly, idempotent, and openWorld hints. The description adds valuable behavioral context by noting that the stage field is authoritative and only stage=commercial represents live inventory, going beyond the annotations. No contradiction.

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, immediately states the action, and contains zero filler. It is perfectly concise and front-loaded.

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 the small number of optional parameters (3), complete schema coverage, and rich annotations, the description provides sufficient context. It covers search dimensions and the key stage nuance. The lack of an output schema is not an issue since this is a search tool, and return format is implied. Minor room for improvement could be mentioning pagination or result scope.

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?

The schema covers all parameters with 100% description coverage, so the baseline is 3. The description adds semantic value by mapping 'maturity, category, or text' to parameters and specifically highlighting that stage is authoritative, which enriches the stage parameter's meaning.

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 'Search the public recipe menu by maturity, category, or text' which is a specific verb+resource. It does not explicitly distinguish from sibling tools like genie_catalog, so it falls short of a 5.

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 provides clear context for when to use the tool ('Search the public recipe menu') and adds important guidance about the stage field being authoritative, with only stage=commercial being live inventory. However, it does not mention alternatives or exclusions.

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