ahk_control_send

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and idempotentHint=false. The description adds context about background operation and reliability compared to WM_CHAR, but does not disclose side effects, potential errors, or behavior on timeout. Since annotations lower the bar, the description adds some value but not rich behavioral detail.

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 concise and front-loaded, with the main behavior in the first sentence. It includes a short usage hint, a compact Args list, and a Returns line. Every sentence earns its place with no redundancy or filler.

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?

The tool is moderately complex (five parameters, background targeting), but the description covers the core use case, the target format, and the return type. With good annotations and a rich input schema, the description is largely sufficient. However, it could better clarify when to use this tool over sibling send tools and what happens on timeout, so a perfect score is not warranted.

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?

The input schema itself provides detailed descriptions for all parameters (text, window, as_keys, control, timeout), so the schema coverage is effectively high. The tool description merely lists parameter names ('text, window/control targets, as_keys, timeout') without adding new meaning, so it does not go beyond the schema. Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Send text or keystrokes to a background window/control via AutoHotkey ControlSend.' This clearly distinguishes the tool from siblings like win_send_keys, type_text, and press_keys by emphasizing background/control targeting and the AutoHotkey ControlSend mechanism.

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 usage context: 'Works without focusing the window' and 'often more reliable than raw WM_CHAR for complex apps.' It also gives a target-format hint with 'Target a HWND with ahk_id <handle>.' However, it does not explicitly name alternative sibling tools or state when NOT to use this tool, so it falls short of a 5.

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