generate_frida_instrumentation

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

No annotations exist, so the description carries the full disclosure burden. 'Generates' usefully signals that the tool emits a script rather than attaching to a process, but 'Active reverse engineering intervention' is ambiguous about whether it touches the live target, and nothing states prerequisites (root/jailbreak, target running or not), side effects, or that the result is script text. For a runtime-manipulation tool with zero annotation coverage this is a substantial gap.

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?

Two compact sentences, front-loaded with the nature of the tool and then the concrete script families. No filler or repetition; the only slack is the vague 'Active reverse engineering intervention' opener.

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?

With no annotations and no output schema, the description should carry the behavioral and return-format burden, but it only establishes what is generated. An agent knows what to ask for but not what comes back, whether the target must be live, or what privileges are needed.

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 100% and both enums are self-explanatory, so the schema does the heavy lifting. The description adds no parameter-level meaning (e.g., how script_type interacts with platform, or what custom_filter matches against), so baseline 3 applies.

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?

States a specific verb and resource ('Generates production-grade Frida dynamic instrumentation scripts') and enumerates the four concrete script families (SSL unpinning, root/jailbreak cloaking, anti-debug hooks, crypto sniffing). It is clearly distinguishable from siblings like patch_binary_executable or neutralize_anti_debugging, which act on the binary rather than emit a script. It stops short of explicitly contrasting itself with those siblings.

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?

'Active reverse engineering intervention' plus the enumerated script types imply the usage context, but there is no explicit when-to-use/when-not statement and no named alternative. An agent must infer that this is the script-generation path versus the direct-action tools in the sibling list.

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