list_recipes

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

The verb 'List' implies a read-only operation, and the description mentions optional filtering behavior. However, with no annotations, it does not explicitly disclose whether the tool is safe from side effects, nor does it describe pagination or access scoping.

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?

A single, front-loaded sentence that conveys the core purpose and optional filters without redundant words.

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 list tool with no output schema and no annotations, the description covers the basic listing action and filters but omits return format, pagination, and filter combination behavior. It is minimally viable but leaves safety-related gaps.

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 description enumerates the three filters and provides type hints for `running` (bool) and `name_contains` (substring), which are absent from the schema (0% coverage). It adds some semantic meaning but leaves ambiguous how `folder_id` is matched and what `running=true` specifically filters.

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 identifies the operation (listing) and resource (recipes), and specifies optional filters. It distinguishes from `get_recipe` which fetches a single recipe, but does not explicitly differentiate from other list-type siblings like `list_recipe_versions`.

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 is provided on when to use this tool versus alternatives such as `get_recipe` or `list_recipe_versions`. It does not mention preconditions, scoping, or typical use cases, leaving the agent to infer applicability.

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