frida_win_com_intercept

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

The description explains the mechanism (hooks CoCreateInstance, patches vtable) and that it logs invocations. However, it does not disclose potential side effects (e.g., process memory changes, crashes) or cleanup requirements. With no annotations, the burden is on the description.

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 clear purpose statement followed by parameter details. It is front-loaded and each sentence adds value. A slightly more structured format (e.g., bullet parameters) could improve readability.

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?

While the description covers purpose and parameters, it lacks output format, error conditions, prerequisites (e.g., Frida running), and behavioral details (e.g., blocking behavior). Given no output schema, more context 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?

The description adds meaningful context beyond the schema: explains `target` as process name/pid, `clsid_or_progid` as CLSID or '*' for all, `method_index` with known vtable indices, and `duration_seconds` default. Since schema coverage is 0%, this is highly valuable.

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 tool's purpose: intercept a COM vtable method call on Windows. It specifies the verb ('intercept', 'hooks', 'patches') and the resource ('COM vtable'), making it distinct from sibling tools like `frida_win_api_monitor`.

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 implies usage for Windows COM interception but does not explicitly state when to use this tool versus alternatives (e.g., other Windows hook tools). No exclusion criteria or context for 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.