frida_disconnect

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

Discloses detaching from process and unloading persistent hooks, but omits error conditions, side effects on other sessions, or whether the operation is reversible. No annotations, so description carries full burden, but is only partially transparent.

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 plus a parameter note, no extraneous words. Front-loaded with purpose, efficient and to the point.

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 tool with one optional parameter and no output schema, the description is mostly complete. Covers core action and effect, though lacks error handling or return value info.

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 has 0% description coverage, but description adds meaning: explains session_id is optional, defaults to active session. Adds value beyond schema structure, though could specify format or constraints.

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?

Description clearly states it disconnects from a Frida session, detaches from process, and unloads hooks. Verb and resource are specific, but does not explicitly differentiate from sibling tools like frida_connect or frida_switch_session.

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?

Implies usage when disconnecting from a session, but no explicit guidance on when to use versus alternatives (e.g., frida_is_connected, frida_switch_session). Lacks when-not-to-use or prerequisites.

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