ahk-mcp

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

The annotations declare readOnlyHint=true, but the description mentions actions like 'enable/disable features' and the schema includes actions like 'set,' 'enable_tool,' 'disable_tool,' etc., which clearly imply write operations. This creates a direct contradiction between the description's implication of mutability and the annotation's declaration of read-only behavior. This is a serious inconsistency that could mislead an agent.

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 brief (two short lines) but under-specified rather than efficiently concise. While it doesn't waste words, it fails to provide essential information that would help an agent understand when and how to use this tool. The structure is basic with no front-loading of critical information.

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 tool with 3 parameters (including a complex nested object), no output schema, and contradictory annotations, the description is inadequate. It doesn't explain what 'settings' actually controls, how actions interact, what the tool returns, or how it differs from similar tools. The combination of vague purpose, missing guidelines, and annotation contradiction leaves significant gaps in understanding.

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 schema already documents all parameters thoroughly. The description adds no additional parameter information beyond what's in the schema. The baseline score of 3 is appropriate since the schema does the heavy lifting, though the description doesn't compensate with any extra context about parameter usage or relationships.

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 'Ahk settings Manage tool settings and enable/disable features' is tautological - it essentially restates the tool name 'AHK_Settings' with minimal elaboration. While it mentions 'manage tool settings and enable/disable features,' this is too vague to clearly distinguish this tool from its many siblings (like AHK_Config, AHK_File_Edit, etc.). It lacks a specific verb+resource combination that would make 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 provides no guidance on when to use this tool versus alternatives. With 30+ sibling tools including AHK_Config (which might overlap with settings management), there's no indication of when this tool is appropriate versus other configuration-related tools. No prerequisites, exclusions, or alternative tools are mentioned.

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