skylight_list_recipes

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

With no annotations, the description carries full burden. It only states that the tool lists recipes for the frame, with no mention of pagination, ordering, filtering, side effects, or required permissions. This is insufficient for behavioral transparency.

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, front-loaded with the key action and resource. No extraneous words. Highly concise.

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 the lack of output schema, single parameter with no description, and no annotations, the description is incomplete. It does not explain what a frame or recipe is, expected output format, or any constraints. A list tool should provide more context.

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 parameter 'frameId' has no description in the schema (0% coverage). The description adds 'for the frame,' implying frameId is the frame identifier, but does not explain its format or whether it's truly optional (since not required). Minimal added value over 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 the verb 'List' and the resource 'meal recipes,' with scope 'for the frame.' This distinguishes it from siblings like get_recipe (single) and create_recipe. However, the term 'frame' is not explained, which may cause slight ambiguity.

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. There are many list tools, but no context on when listing recipes is appropriate or when to use other recipe tools (e.g., get_recipe, create_recipe).

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