meal_search

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

No annotations provided; description only states 'search by name'. Does not disclose whether search is fuzzy, case-sensitive, paginated, or any other behavioral traits beyond the basic operation.

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?

Single sentence, highly concise and front-loaded with essential information. However, it could be slightly expanded to include behavioral context without losing brevity.

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 simple search tool with one parameter and no output schema, the description is minimal but does not cover expected behavior like result ordering or what fields are searched beyond name.

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 has 0% description coverage for the single 'query' parameter. Description adds 'by name' implying query is a meal/recipe name, but lacks details on format, partial matching, or constraints.

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 verb 'search', resource 'meals/recipes', and the search attribute 'by name'. This differentiates it from sibling tools like meal_filter_by_ingredient or meal_random.

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?

No guidance on when to use this tool versus alternatives such as meal_filter_by_area or meal_categories. Agent must infer usage from semantics alone.

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