ahk-mcp

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

Annotations indicate read-only and idempotent operations, which the description aligns with by focusing on discovery/search. The description adds valuable context beyond annotations: token usage estimates (50-1,000 tokens), progressive loading benefits, and detail level impacts, though it doesn't cover rate limits or error behaviors.

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 well-structured with clear sections (Examples, Categories, Detail Levels, Use Cases), but it includes some redundant information like repeating detail level token estimates. Most sentences are purposeful, though it could be slightly more streamlined.

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 (search/discovery with token optimization) and lack of output schema, the description is mostly complete. It explains the tool's role, parameters, and usage contexts effectively, but doesn't detail the exact format of search results or error handling.

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 parameters thoroughly. The description provides examples and categorizations that reinforce parameter usage but doesn't add significant semantic value beyond what's in the schema, meeting the baseline for high 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: 'Efficiently discover available AHK tools without loading all 35+ tool definitions upfront.' It specifies the verb ('discover') and resource ('AHK tools'), and distinguishes it from siblings by explaining its role in progressive tool discovery versus direct tool execution.

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 explicit guidance on when to use this tool versus alternatives. It includes 'Use Cases' section detailing scenarios like 'Initial exploration', 'Targeted search', and 'Full details', and references sibling tools like 'AHK_Config' and 'AHK_Analytics' for related but distinct purposes.

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