nexo_hook_runs

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

No annotations are provided, so the description must convey behavior. It explains that the tool reads from the hook_runs table (a read operation) and returns a health summary. This adequately discloses behavior for a read-only list tool, though more detail on output format could be added.

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 concise: two substantive sentences plus context. It is front-loaded with the main action and well-structured, without unnecessary 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?

Given the tool's 5 parameters (all documented), no output schema, and complexity, the description provides sufficient context to understand its purpose, use case, and output behavior. It answers the likely questions an agent would have.

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 each parameter has a clear description. The description adds minimal extra meaning beyond the schema, aligning with the baseline score of 3 for high-coverage tools.

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 'List recent hook lifecycle runs and per-hook health summary', specifying the verb 'List' and the resource. It further explains the context of NEXO hooks and the purpose of checking pipeline health, which distinguishes it from sibling lifecycle tools.

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 indicates the tool is for answering 'is the hook pipeline healthy?' without needing dashboard or log grepping, implying when to use it. However, it does not explicitly contrast with siblings like nexo_lifecycle_status, so scores slightly below 5.

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