ahk_control_send

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

Annotations provide limited behavioral info (readOnlyHint=false, destructiveHint=false). Description adds that it works without focusing, but does not disclose side effects, error handling, or permissions. Adequate but not rich.

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?

Extremely concise: two sentences plus Args/Returns. Front-loads key purpose and usage hint. No superfluous text.

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?

Covers basic purpose and usage, but lacks explanation of parameter relationships (e.g., control vs. window), timeout behavior, and output details. Output schema exists but description only says 'JSON with the AHK run result'. Satisfactory for single-param tool with rich schema.

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 0%, so description must compensate, but it merely lists parameter names without adding meaning. The input schema itself has descriptions, but the tool description offers no additional semantics or context.

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?

Description clearly states the tool sends text/keystrokes to background windows via AutoHotkey ControlSend, distinguishes from siblings by emphasizing background operation and reliability over WM_CHAR. Explicitly mentions targeting via 'ahk_id <handle>'.

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?

Provides clear guidance on when to use (background windows, complex apps) and advantages over WM_CHAR, but does not explicitly state when not to use or compare with siblings like win_send_keys. Implied differentiation is present.

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