ahk-mcp

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

Annotations indicate readOnlyHint=true and idempotentHint=true, which the description doesn't contradict. The description adds context about the search technology (FlexSearch) and scope (AutoHotkey v2 docs), which is useful beyond annotations. However, it doesn't disclose behavioral traits like rate limits, authentication needs, or result format details that would be helpful for 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 and front-loaded with essential information in two sentences. The first line 'Ahk doc search' is somewhat redundant but serves as a header. The second sentence efficiently conveys the core functionality and scope. There's minimal waste, though it could be slightly more polished.

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 (4 parameters, no output schema), the description is adequate but not complete. It covers the purpose and technology but lacks details on result format, error handling, or integration context. With annotations providing safety hints, the description meets minimum viability but leaves gaps in operational guidance.

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%, so the schema fully documents all parameters (query, category, offset, limit). The description mentions 'search' and categories (functions, variables, classes, methods), which aligns with the schema but doesn't add significant semantic value beyond what's already in the structured fields. 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 clearly states the tool's purpose: 'Full-text search across AutoHotkey v2 docs using FlexSearch' with specific resources listed (functions, variables, classes, methods). It distinguishes from most siblings by focusing on documentation search, though it doesn't explicitly differentiate from AHK_Tools_Search which might be similar. The verb 'search' is specific and the scope is well-defined.

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. It doesn't mention sibling tools like AHK_Tools_Search or AHK_Library_Search that might overlap in functionality, nor does it specify scenarios where this documentation search is preferred over other search or information retrieval tools in the server. Usage is implied but not explicitly stated.

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