frida_uninstall_hooks

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

Without annotations, the description conveys behavioral traits well: it stops hooks, clears the list, and notes that collected messages persist. This is sufficient disclosure for a tool with no destructive hint annotations.

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 two concise sentences, front-loaded with the main action and followed by a clarifying detail. No extraneous words.

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 tool with no output schema, the description fully explains the behavior (unloading hooks, message retention) leaving no ambiguity.

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?

There are zero parameters and 100% schema coverage, so the description does not need to add parameter details. Baseline of 4 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 the tool unloads all persistent hook scripts, stops active hooks, and clears the hook list. The verb 'unload' and resource 'persistent hook scripts' are specific, and it distinguishes from sibling tools like 'frida_install_hook' or 'frida_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?

The description mentions 'in the current session' but provides no explicit when-to-use or when-not-to-use guidance. It does not compare with alternatives or indicate if selective unloading is possible, leaving the agent to infer usage context.

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