add_hook

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

The phrase 'calls stream to disk' suggests side effects, but no details on mutability, persistence, or reversibility. With no annotations, the description fails to adequately disclose 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?

The description is a single sentence, concise and front-loaded. It could slightly expand on key points without becoming verbose.

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 an operation like hooking a function, the description omits critical details: return values, side effects, prerequisites (e.g., valid session), and cleanup. With no output schema, completeness is lacking.

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 parameter 'target' is explained with format hints (module!export or hex address), adding value beyond the schema. However, 'session_id' is left undefined, and with 0% schema description coverage, more detail is expected.

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 specifies the action 'Hook a function' with acceptable target formats (module!export or hex address), clearly indicating the tool's purpose. It stands out from siblings like attach or detach, but lacks explicit differentiation.

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 over alternatives, no prerequisites or context for invocation. The description only states what it does, not when it's appropriate.

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