Create cookbook

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

Annotations indicate it's a non-destructive write. The description adds valuable behavioral details: without filter it matches all recipes, the filter uses a custom query language, invalid filters return a 422. This goes beyond annotations.

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 concise sentences with no wasted words. First sentence defines the tool, second provides key behavioral nuance. Front-loaded and efficient.

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 creation tool with four parameters and no output schema, the description covers the core behavior, filter semantics, and error scenario. It doesn't state what is returned (likely the created object), but the missing info is standard. Overall fairly complete.

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 50%. The description adds meaning for 'query_filter' (explaining it's Mealie's query language and default behavior) and for 'name' (cookbook as named view). However, 'description' and 'is_public' get no extra clarification. Baseline 3 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 the tool creates a cookbook, defined as a named, saved view of recipe collection. It distinguishes from siblings like delete_cookbook, list_cookbooks, etc., and explains the filter behavior.

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 creating a saved view. It includes a hint that complex filters are easiest to build in the web UI, providing some context about when to use this tool versus other interactions. However, it doesn't explicitly state alternatives or exclusions.

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