frida_android_frida_server_start

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

Behavioral aspects beyond the simple verb 'Start' are missing. No annotations exist, and the description does not disclose side effects, blocking behavior, or post-conditions. For a mutation tool, this is insufficient.

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 too terse—only six words. While concise, it sacrifices necessary detail, making it under-specified for an agent to use correctly.

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 tool's complexity (4 parameters, no annotations, no output schema), the description is severely lacking. It fails to cover return values, error conditions, or dependencies, leaving the agent with insufficient context.

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 adds no information about parameter meanings or usage. All four parameters (adb_serial, remote_path, as_root, listen_address) are left unexplained.

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 verb 'Start' and resource 'frida-server' on an Android device. However, it does not differentiate from sibling tools like 'frida_android_frida_server_setup' or 'frida_android_frida_server_install', which are distinct operations.

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 versus alternatives. Prerequisites (e.g., server must be installed) or scenarios (e.g., already running) are not mentioned.

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