frida_win_dotnet_hook_method

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

With no annotations, the description carries the burden. It discloses that the tool hooks and logs invocations, attempts CLR bridge with fallback, and has a default duration. However, it does not explain the mutation's permanence, cleanup, or how logs are accessed, leaving gaps in 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?

The description is concise (7 lines), front-loads the purpose, and uses a clear bullet-like list for parameters. Every sentence adds value, with no redundancy or fluff.

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?

The description explains parameters and fallback behavior but lacks details on output (e.g., where logs go, return value) and does not indicate if the tool is blocking or async. Given the absence of an output schema, more completeness would be beneficial.

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?

Since schema coverage is 0%, the description fully explains each parameter beyond the schema's titles. It provides examples ('mscorlib'), clarifies target as 'name or pid', and specifies defaults. This adds significant value for correct invocation.

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 ('Hook a .NET method'), the resource ('.NET method'), and the platform ('Windows'). It also distinguishes from siblings by specifying .NET on Windows, and mentions fallback mechanisms, making the purpose unambiguous.

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?

The description does not explicitly guide when to use this tool versus alternatives (e.g., frida_hook_native_function). While the name and platform hint imply usage for .NET on Windows, no direct comparison or exclusion criteria are provided.

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