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 using terms like 'view' and 'track'. The description adds value by listing specific actions (summary, tool_stats, etc.) and mentioning data export and clearing, but it does not detail behavioral aspects like rate limits, authentication needs, or error handling beyond what annotations imply.

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 appropriately sized and front-loaded, starting with the core purpose and then detailing actions and usage. Every sentence adds value, but it could be slightly more structured by separating action explanations from usage context for even clearer readability.

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 (analytics with multiple actions), annotations cover safety (read-only, idempotent), and schema coverage is complete, the description is largely sufficient. However, without an output schema, it does not explain return values or data formats, leaving a minor gap in completeness for an analytics tool.

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 parameters like 'action', 'toolName', and 'limit'. The description adds minimal semantics by listing action names and hinting at their purposes (e.g., 'tool_stats' for specific tool), but it does not provide additional meaning beyond the schema's enum and descriptions, 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 with specific verbs ('view', 'track') and resources ('tool usage analytics and performance metrics'), distinguishing it from siblings by focusing on analytics rather than file operations, debugging, or other functions. It explicitly lists the available actions, making the scope concrete.

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 the tool ('diagnose tool issues or optimize workflows'), but it does not explicitly state when not to use it or name alternatives among the sibling tools. This gives good guidance but lacks exclusion criteria or direct sibling comparisons.

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