run-hooks

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

The description transparently reveals that the tool both retrieves and executes hooks: 'get all hooks' and 'execute the matching hooks' instructions.' No annotations are provided, so the description carries the full burden. It clearly conveys the dual nature, but could further detail what execution entails (e.g., 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?

The description is three sentences long, with no wasted words. The first sentence states the purpose, the second gives usage guidance, and the third provides a concrete example. It is well-structured and efficient.

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?

The tool has one parameter, no output schema, and no annotations. The description explains what it does and when to use it, but does not describe the return format or the nature of hook execution. For a tool that also performs actions, more details about execution behavior would improve completeness.

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 input schema covers 100% of parameters with a description and an enum. The description adds an example event ('on-task-completed'), but this does not significantly add meaning beyond the schema. Per guidelines, with high schema coverage, baseline is 3, which is appropriate.

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 'Get all hooks matching a specific event type,' using a specific verb and resource. It distinguishes itself from sibling tools like create-hook, delete-hook, and list-hooks by focusing on matching events and executing 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 explicitly states when to call the tool: 'The AI should call this when an event occurs and execute the matching hooks' instructions.' It provides a concrete example with the event 'on-task-completed.' However, it does not explicitly mention when not to use it or alternatives, but the example and sibling list provide sufficient context.

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