frida_objc_register_class

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

No annotations are provided, so the description must disclose behavioral traits. It mentions 'runtime registration' implying mutation, but does not clarify side effects (e.g., whether re-registering a class overwrites, or if registration is persistent per session) or error conditions.

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 extremely concise with a two-line header and a bullet list of parameters. Every sentence is useful and there is no fluff. It is front-loaded with the main purpose.

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 relatively complex operation like registering a new ObjC class at runtime, the description is minimal. It lacks details on return values, success/error scenarios, and the lifecycle of the registered class. Given the absence of an output schema and no annotations, more context would be beneficial for safe and correct usage.

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 the description adds meaning by explaining each parameter: target as 'process name or pid', name as 'class name', super_class as 'name of the superclass', and methods_js as 'JS object literal for methods'. It provides clarity beyond the bare schema property names, though it could elaborate on the structure of methods_js.

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 action: 'Register a new ObjC class at runtime via ObjC.registerClass.' It specifies the verb (register) and resource (ObjC class), distinguishing it from sibling tools like frida_objc_call_method or frida_objc_choose.

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 on when to use this tool versus alternatives, nor any prerequisites or conditions. For example, it does not mention that a Frida session must be active or that the process must be suspended for class registration to take effect.

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