run_script

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

No annotations provided, so description carries full burden. Discloses that code execution occurs and that Java bridge is auto-imported, but does not mention potential side effects (e.g., memory corruption, app crashes) or permissions needed.

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 sentences, front-loaded with main action, no wasted words. Every sentence adds necessary context.

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?

For a simple one-parameter tool with no output schema, description covers core functionality and a key detail (Java bridge auto-import). Could mention expected output format (e.g., console.log results), but minimal sufficient.

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?

Adds value beyond schema: 'Java bridge is auto-imported, so Java.perform(), Java.use(), etc. work directly' informs the agent about implicit capabilities of the js_code parameter, not just that it's JavaScript code.

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?

Clearly states 'Execute custom Frida JavaScript code' with specific verb 'Execute' and resource 'Frida JavaScript code'. Distinguishes from siblings by mentioning Java bridge auto-import, which is unique to this tool among siblings like run_java or hook_native.

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?

Implied usage (execute custom Frida JS code) but no explicit guidance on when to use this vs alternatives like run_java or hook_native. Does not mention prerequisites or context.

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