frida_script_reload

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

With no annotations, the description must disclose behavioral traits. It only states that name and kind are preserved, but does not explain side effects (e.g., state reset, permission requirements, whether the script must be currently running). This is insufficient for a reload operation.

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 (one sentence) but lacks structure. Given the parameter count, it would benefit from more detail or formatting. It is adequate but not exemplary.

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 7 parameters, no output schema, and no parameter descriptions. The description provides only the core action, leaving out essential context like parameter purposes, prerequisites, and return behavior. The agent cannot effectively use this tool based solely on the description.

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 description coverage is 0% and the description does not explain any of the 7 parameters. The agent gets no guidance on what session_id, js_code, script_path, runtime, parameters, or auto_perform mean or how to use them.

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 action ('Reload'), resource ('a long-running script'), and what is preserved ('its name and kind'). This distinguishes it from sibling tools like frida_script_load and frida_script_unload.

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 implies usage (reload a script while keeping name/kind) but provides no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives or prerequisites.

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