frida_set_exception_handler

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

Describes hooking Process.setExceptionHandler and captured data (type, address, register context), but lacks details on side effects, removal, or prerequisites. No annotations provided, so description carries burden but is adequate.

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?

Three sentences, front-loaded purpose, efficient parameter explanations. No redundant information.

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?

Covers purpose, mechanism, and parameters. Missing return value info and explicit statement that handler is removed after duration. Almost complete for a simple tool.

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 meaning beyond schema: 'target' clarified as process name or pid, 'duration_seconds' explained with default 10. Compensates for 0% schema description coverage effectively.

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 the verb 'install' and resource 'exception handler' to catch crashes. Distinguishes itself from siblings by focusing on exception handling, not other hooks or debugging tasks.

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 explicit when-to-use or when-not-to-use guidance. Implies usage for catching crashes, but doesn't compare with alternatives like frida_hook_native_function or other handlers.

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