frida_win_crypto_hook

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

Discloses hooked functions and logged info (key handle, data sizes, operation type). Lacks mention of side effects, performance impact, required privileges, or behavior during failures. No annotations to compensate.

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?

Concise, with front-loaded platform and purpose. Parameter descriptions inline but clear. No wasted words, though structure could be improved by separating parameter details.

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?

Adequate for a simple hook tool with two parameters and no output schema. Missing details on how to stop capture, return format, or error handling.

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 meaningful context beyond schema: explains 'target' as process name or pid, and 'duration_seconds' as capture time. Schema coverage is 0%, so description provides necessary detail.

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?

Cleerly states it hooks Windows CryptoAPI and BCrypt encryption/decryption functions, listing specific hooked functions and logged data. Distinguishes from siblings by platform prefix '[Windows]', but could further differentiate from frida_crypto_hook.

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 platform hint but no explicit when-to-use or when-not-to-use. Does not mention alternatives like frida_crypto_hook, nor criteria for selection.

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