frida_script_unload

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

No annotations exist, so the description must disclose behavior. It only says 'unload' without explaining side effects (e.g., whether the script is destroyed, if it can be reloaded, or impact on the session). The term 'long-running' is vague and not defined.

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 concise sentence. It is efficient but may be too brief, missing opportunities to add crucial information without bloat.

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 no output schema and no annotations, the description lacks necessary context such as return values, error conditions, prerequisites (script must be loaded), and the relationship to `session_id`. This is insufficient for a tool with 2 parameters and no other documentation.

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 0%, and the description provides no additional meaning for parameters. `script_id` is merely mentioned, but no format or source is given. `session_id` is not addressed at all, leaving the agent uninformed about its purpose or when to provide it.

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 verb 'unload' and the resource 'long-running script', and references the key parameter `script_id`. Among many script-related tools (load, reload, list), this clearly distinguishes it as the unload operation. However, it does not clarify what qualifies as 'long-running'.

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 usage context is provided. The description does not indicate when to use this tool versus alternatives (e.g., `frida_script_reload` or `frida_script_eternalize`), nor does it mention prerequisites like the script being previously loaded.

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