ahk-mcp

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

Annotations declare readOnlyHint=true and idempotentHint=true, indicating this is a safe, repeatable operation. The description adds that it 'automatically injects' context, suggesting it performs analysis and returns documentation snippets rather than modifying data. However, it doesn't disclose behavioral traits like rate limits, authentication needs, or what 'inject' means operationally (e.g., returns text vs. modifies a file). With annotations covering safety, the description adds minimal but not rich context.

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 two short sentences that efficiently state the tool's function. It's front-loaded with the core purpose and avoids unnecessary elaboration. However, the first line 'Ahk context injector' is redundant with the tool name and could be omitted for better structure, slightly reducing efficiency.

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 moderate complexity (5 parameters, no output schema), the description is minimally adequate. It explains what the tool does but lacks details on return values (no output schema), error conditions, or integration with sibling tools. With annotations covering safety, the description meets basic needs but leaves gaps in operational context that could help an agent use it effectively.

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?

Schema description coverage is 100%, with all 5 parameters well-documented in the schema itself (e.g., userPrompt is 'required', contextType has enum values, maxItems has range). The description mentions 'analyzes user prompts and LLM thinking' which aligns with the userPrompt and llmThinking parameters, but adds no meaningful semantics beyond what the schema already provides. Baseline 3 is appropriate given high schema coverage.

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 'analyzes user prompts and LLM thinking to automatically inject relevant AutoHotkey v2 documentation context', which provides a clear verb ('analyzes' and 'inject') and resource ('AutoHotkey v2 documentation context'). However, it doesn't distinguish this tool from its many siblings, particularly AHK_Doc_Search which likely also deals with documentation. The purpose is understandable but lacks sibling differentiation.

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?

No guidance is provided on when to use this tool versus alternatives. With 31 sibling tools including AHK_Doc_Search, AHK_Analyze, and AHK_Smart_Orchestrator, the description offers no context about appropriate use cases, prerequisites, or when other tools might be more suitable. The agent must infer usage from the name and description alone.

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