scaffold_hook

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

With no annotations, the description carries full burden. It states the basic action but omits details like whether existing hooks are overwritten, required permissions, side effects, or error states. The list of templates adds some context but does not cover behavioral traits.

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 followed by a list of templates. Extremely concise with no wasted words. Front-loaded with the verb and object.

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 simplicity (3 params, 1 required, no output schema) and good schema coverage, the description is adequate but lacks behavioral details and return value description. It covers the core action but leaves gaps for an agent.

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%, so baseline is 3. The description adds value by listing the actual template names (auto-fix-on-start, etc.), which concretely clarifies the template_id parameter beyond the schema's 'Template id from list_hooks'.

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 tool installs a Claude Code hook from the toolkit's template catalog, listing the available templates. This provides a specific verb ('Install') and resource ('hook from catalog'), distinguishing it from sibling tools like list_hooks.

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 (e.g., list_hooks for viewing templates, or other hook management tools). No prerequisites or context for choosing a template are provided.

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