ahk-mcp

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

The description adds valuable behavioral context beyond the annotations: it explains validation rules (.ahk extension validation), safety features (prevents accidental overwrite), and operational modes (dry-run previews). While annotations already indicate destructiveHint=true, the description elaborates on what 'destructive' means in this context with the overwrite prevention logic.

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 efficiently structured with a clear opening statement followed by bullet points highlighting key features. Every sentence earns its place by providing distinct value, and the information is appropriately front-loaded with the core purpose stated first.

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 file creation tool with 6 parameters, destructiveHint=true, and no output schema, the description provides good contextual coverage. It explains behavioral constraints, safety features, and operational modes. The main gap is the lack of information about return values or error conditions, which would be helpful given the complexity.

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?

With 100% schema description coverage, the input schema already documents all 6 parameters thoroughly. The description doesn't add significant parameter-specific semantics beyond what's in the schema, though it mentions 'full path interception support' which relates to the filePath parameter's behavior.

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 specific action ('Create a new AutoHotkey v2 script on disk') and resource type, distinguishing it from sibling file tools like AHK_File_Edit, AHK_File_List, or AHK_File_View. It explicitly mentions 'full path interception support' which adds specificity beyond a generic file creation tool.

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 clear context for when to use this tool (creating new AHK scripts with specific features like path interception and directory creation). It mentions the sibling tool AHK_File_Active for setting active files, but doesn't explicitly state when NOT to use this tool or provide alternatives for similar operations.

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