sassy_hooks_list

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

With no annotations provided, the description carries the burden of behavioral disclosure. It clearly indicates a read-only listing operation and explains the purpose of hooks, but it does not mention permissions, auth, or output size. The non-destructive nature is implied by 'list,' but not explicitly stated.

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 exactly three sentences, front-loading the core purpose and then adding context about hooks and the next step. Every sentence earns its place, with no fluff or repetition.

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 list tool with an output schema, the description is complete: it defines the domain (hooks as playbooks), states that all available hooks are listed, and points to the activation tool. The output schema covers return format, so no additional description is needed.

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 the description adds value by explaining what is listed (operational hooks) and the meaning of hooks. With 100% schema coverage on an empty schema, the baseline for zero parameters is 4; there is no parameter-specific information to add.

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 opens with a specific verb and resource: 'List all available operational hooks.' This clearly states the tool's function and scope, and it is distinct from sibling tools like sassy_hooks_activate, which loads a hook, and sassy_hooks_suggest, which presumably suggests 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?

The description explains what hooks are and tells the agent to use sassy_hooks_activate to load one after listing, giving clear context for when listing is useful. However, it does not explicitly contrast with sassy_hooks_suggest or state exclusions, so it stops short of a full when-to-use guide.

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