mealie_search_recipes

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits, but it only mentions support for queryFilter syntax. It does not disclose whether the operation is read-only, how pagination behaves, or potential side effects. The sparse description leaves the agent without crucial behavioral context.

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 filler. It front-loads the primary purpose and adds a key feature (queryFilter syntax) in a compact manner. Every word earns its place, making it an excellent example of minimalistic structure.

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?

Despite having an output schema, the description is insufficient for a tool with six parameters, no annotations, and many sibling tools. It lacks context about pagination, ordering, default behavior, or how this search differs from other recipe-related tools. The description feels incomplete for the complexity involved.

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 0%, so the description must compensate by explaining parameter meanings, but it does not. The six parameters (page, search, order_by, per_page, query_filter, order_direction) are not mentioned or described. The only hint is the reference to 'queryFilter syntax,' which is too vague to understand the query_filter parameter's format or usage.

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's function with a specific verb and resource: 'Search Mealie recipes.' It also distinguishes itself from sibling tools like mealie_get_recipe or mealie_search_chefkoch by specifying 'Mealie' and mentioning 'queryFilter syntax' for advanced filtering.

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 no explicit guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or when to prefer another search tool like mealie_search_chefkoch. The intended usage is implied as a general search, but no concrete direction is given.

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