hook_jsvmp_interpreter

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

With no annotations, the description fails to disclose behavioral traits like side effects, resource usage, or reversibility. 'Install a JSVMP runtime probe' does not indicate whether the probe is persistent, whether it modifies the JS environment, or what happens after installation.

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?

While a single sentence is concise, it omits critical information, making it under-specified rather than efficiently structured. Every sentence should add value, but here it only states the basic action without details.

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 8 parameters and no output schema, the description is highly incomplete. It does not explain what the tool returns, how to interpret results, or how parameters interact. The agent lacks enough context to use the tool effectively.

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 tool description provides no explanation for any of the 8 parameters (e.g., mode, persistent, script_url). The agent cannot infer parameter usage or impact, severely hampering correct invocation.

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 a verb ('Install') and a resource ('JSVMP runtime probe'), indicating the tool sets up a probe for JSVMP. However, it lacks specificity about what 'runtime probe' entails and does not differentiate from similar tools like 'hook_function' or 'trace_vmp_for_sign'. The purpose is vaguely clear but not precise.

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 on when to use this tool versus alternatives such as 'hook_function' or 'disassemble_wasm'. The description does not mention prerequisites, suitable scenarios, or exclusions, leaving the agent without context for selection.

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