skylight_list_recipes

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

The readOnlyHint annotation already communicates that this is a read operation, and the description merely restates the list behavior. It adds little beyond the frame scope and does not disclose return format, pagination, empty-list behavior, or whether frameId can be omitted.

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 a single, front-loaded sentence with no filler. Every word contributes to the core meaning, and there is no wasted content.

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 one-parameter read-only list, the description is minimally viable, but it leaves important gaps: no return-shape information, no clarification of how recipes differ from meals, and no guidance on using related list/get tools. It is adequate but not self-sufficient.

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%, and the description only says 'for the frame,' which essentially restates the frameId property name. It provides no information about the ID format, how to obtain valid frame IDs, or the fact that frameId appears to be optional.

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 names a specific verb and resource: 'List meal recipes for the frame.' It is not a tautology and clearly conveys the action and object. However, it does not explicitly distinguish this from closely related sibling tools like skylight_list_meals or skylight_get_recipe.

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?

There is no guidance about when to use this tool versus alternatives such as skylight_list_meals, skylight_get_recipe, or skylight_list_meal_categories. The phrase 'for the frame' gives some context but does not help the agent choose among related recipe/meal tools.

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