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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral content beyond that: with no output schema, it discloses the returned fields (name, cost estimate, skill_url, script_url) and notes script_url is conditional on a recipe being official, which is useful shape information an agent cannot get elsewhere.

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 tight sentences: the first establishes what recipes are, the second enumerates the return payload with the conditional case parenthesized. No filler, no repetition of the title or annotations.

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 zero-parameter read tool with no output schema, the description supplies the domain framing and return-field list an agent needs to call and interpret it. Minor gaps remain (no statement of ordering, pagination, or filtering scope), but nothing essential is absent.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter-level meaning is missing.

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 defines the resource domain (recipes are skills for common jobs built from Superpowers tools) and implies enumeration via the 'Returns name, cost estimate, skill_url...' clause, which reads as a listing of what each item contains. It is clear what the tool produces, but it never states scope explicitly (all recipes? all available to the caller?) nor contrasts itself with the sibling get_recipe, which fetches a single 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 when-to-use guidance and no routing to alternatives. A sibling named get_recipe exists, yet the description never says to use list_recipes to discover recipes and get_recipe to fetch one, leaving the agent to infer the split from the names alone.

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