list_saved_recipes

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

Discloses that it fetches details per recipe and sorts by most recent, which is behavioral context not captured by schema. Without annotations, this adds useful transparency, though the exact nature of 'details' could be clearer.

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. Purpose is front-loaded, and the performance hint is efficiently added.

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 one optional parameter and no output schema, the description is fairly complete: it explains what the tool returns (favorites, order, details) and provides a performance warning. Could mention that no other parameters exist, but that's implicit.

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 only parameter 'limit' has 0% schema description coverage, but the description adds meaning by advising to keep limit low and stating the default (12), which compensates for the schema gap.

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 it lists saved/favorite recipes, sorted by most recent first. The verb 'list' and resource 'saved recipes' are specific, and it distinguishes from siblings like get_recipe (single) and random_recipes.

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?

Provides guidance to keep limit low due to per-recipe detail fetching, which helps with performance. However, it does not explicitly mention when to use this tool versus alternatives like searching for recipes.

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