frida_gum_script_load

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

The description is minimal and does not disclose key behaviors such as automatic script unload after the bounded window, blocking behavior, or error handling. With no annotations, the description fails to adequately explain what happens during and after execution.

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?

Although the description is only one sentence, it is under-specified and omits crucial information. Conciseness should not compromise completeness; here, important details are missing.

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 lack of output schema, annotations, and parameter descriptions, the description is far from complete. It does not explain return values, side effects, or how parameters influence behavior, leaving the agent with insufficient information.

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 description does not elaborate on any of the four parameters (target, name, source, duration_seconds). With 0% schema description coverage, the agent receives no additional semantic context beyond parameter names and types.

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 'Call GumJS Script.load() for a bounded window', indicating a specific function call with a time-limited scope. It distinguishes from the sibling 'frida_script_load' by implying a bounded execution window, but the term 'bounded window' remains vague.

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 is provided on when to use this tool over alternatives like frida_script_load or other script-related tools. There is no context on prerequisites or use cases.

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