list_recipes

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

Beyond the annotations (readOnlyHint, idempotentHint), the description discloses that there is no server-side name search, the filter is applied client-side, and it may return fewer results than limit. This is valuable behavioral context not covered by annotations. The return format is also specified.

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 concise and well-structured: a brief one-line purpose, a relevant note, and clear Args/Returns sections. Every sentence provides useful information without unnecessary elaboration.

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 list tool, the description is complete. It covers parameters, return fields, and a critical behavioral caveat. The output schema existence and annotations further complete the picture, so no essential information is missing.

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 input schema provides only titles and defaults, with no descriptions. The description's Args section fully explains both parameters: limit as 'Maximum recipes to fetch before filtering' and name_contains as 'Case-insensitive substring filter applied client-side.' This adds complete meaning beyond the schema.

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 'List saved recipes' with a specific verb and resource. It distinguishes from sibling tools by targeting recipes specifically, while the note about client-side filtering adds additional clarity about the tool's scope.

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 like get_recipe or list_batches. The note about raising limit is a parameter usage tip, not a tool-selection guideline. There is no mention of when not to use it.

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