Attach to Process

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

No annotations provided, so description carries full burden. While it mentions re-attachment on detach/crash, it does not disclose error handling, prerequisites like permissions, or whether re-attaching after crash works seamlessly. More detail would improve transparency.

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 efficient sentences. First sentence states the action, second provides critical usage rule. No unnecessary words, and the critical instruction is front-loaded.

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 simple tool (1 param, no output schema), the description covers essential usage and re-usage conditions. Could mention what happens on success or error, but is largely complete for an attach action.

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 coverage is 100% and the parameter description 'Process ID (number) or Process Name (string, e.g. 'notepad.exe')' adds concrete examples and clarifies the two allowed types, going beyond the schema definition.

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 'Attach Frida to a process' with a specific verb and resource. It distinguishes from sibling tools like 'detach' and 'load_script' by focusing on the attachment action.

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?

Provides explicit usage instructions: 'AI MUST call this first, and MUST call it again whenever any other tool reports that the process is detached or crashed.' This tells the agent when to use and when to re-use the tool.

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