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

Annotations already cover the read-only, idempotent, non-destructive profile, so the description is not required to restate safety. It does add genuinely new context: the contents returned (SKILL.md, cost, script_url) and the trust caveat that community recipes come from other users, with an instruction to disclose behavior to the user before following it. It stops short of noting failure modes or whether fetching has side effects.

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 sentences, both front-loaded and free of filler. The return contents come first, followed by the community-recipe caveat, so the most decision-relevant information leads.

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?

With no output schema, the description usefully enumerates the return shape, and it flags the community-recipe trust issue. It is nearly complete for a simple single-param read tool, though it could be clearer about the read-then-run workflow relative to run_recipe.

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 coverage is 100% and the schema already documents the single 'recipe' parameter as a slug from list_recipes. The description adds no syntax, format, or sourcing detail beyond that, so the baseline 3 applies.

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?

States a specific verb (Read) and resource (a recipe) and enumerates exactly what it returns: SKILL.md steps, inputs, typical cost, and script_url. An agent can distinguish this from list_recipes (enumeration) and run_recipe (execution) without opening a schema.

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 implies usage by describing the SKILL.md as 'the steps to follow with Superpowers tools', suggesting this is the read-before-run step, and adds a caution for community recipes. However, it never explicitly states when to use this versus run_recipe or list_recipes, leaving the routing to inference.

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