ahk-mcp

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

Annotations indicate openWorldHint=true and destructiveHint=true, suggesting this tool can modify system state and has open-ended behavior. The description adds context by mentioning TCP listening, proxying, and traffic capture, which aligns with the destructive hint (e.g., network operations). However, it does not disclose additional behavioral traits like rate limits, error handling, or specific destructive effects beyond what annotations imply.

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 two sentences that directly state the tool's function, front-loaded with the main action. There is no wasted text, but it could be slightly more structured by explicitly mentioning the 'mode' parameter's role. Overall, it is efficient and to the point.

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 tool's complexity with 10 parameters, nested objects, and no output schema, the description is incomplete. It covers the high-level purpose but lacks details on return values, error conditions, or how parameters like 'mode' affect behavior. Annotations provide some context, but without an output schema, the description should do more to explain expected outcomes.

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 input schema has 100% description coverage, so parameters are well-documented in the schema itself. The description does not add meaning beyond the schema, as it only mentions high-level concepts like TCP listening and proxying without detailing parameter interactions or semantics. With high schema coverage, the baseline score of 3 is appropriate.

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 states the tool 'Starts a TCP listener for AutoHotkey /Debug and optionally proxies to a real debug adapter while capturing traffic,' which provides a clear verb ('Starts') and resource ('TCP listener'), but it lacks specificity about the 'mode' parameter that controls different actions (start, stop, status, etc.). It distinguishes from siblings like AHK_Debug_DBGp by focusing on TCP listening and proxying, but the purpose is somewhat vague without mentioning the control actions.

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 provides no explicit guidance on when to use this tool versus alternatives, such as AHK_Debug_DBGp or other debugging-related siblings. It mentions optional proxying but does not specify use cases, prerequisites, or exclusions, leaving the agent with minimal context for selection.

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