frida_intercept_objc_method

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

No annotations provided, so description carries full burden. It discloses that invocations are logged, arguments up to 6 beyond self/sel are captured, and duration_seconds controls hook lifetime. This is fairly transparent though it omits potential side effects or cleanup details.

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 concise, with a single-line summary followed by a compact explanation of key parameters. Every sentence adds value, no waste.

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 complexity of hooking and no output schema, the description is mostly adequate but lacks mention of return values (logs), prerequisites (running Frida session), or how to stop the hook early.

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 0%, so description must compensate. It explains class_name and method_name with examples, and mentions duration_seconds. However, the 'target' parameter is not explained, and the note about capturing arguments is about behavior, not a parameter.

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 it hooks a specific ObjC method and logs invocations. The verb 'Hook' and resource 'ObjC method via Interceptor' are specific. It distinguishes from other hook tools in the sibling list like frida_hook_native_by_offset.

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 examples for class_name and method_name, and mentions duration_seconds. However, no explicit guidance on when to use this tool vs alternatives like frida_objc_call_method or frida_hook_native_function, nor when not to use it.

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