send_input

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only mentions that input is sent via ydotool, without revealing potential side effects, error conditions, or required system state (e.g., display availability). This is insufficient for a tool with multiple modes.

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 with only two sentences. It front-loads the main purpose and provides a specific tip. While more detail could be added, the current structure is efficient and avoids unnecessary verbosity.

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?

Despite the presence of an output schema, the description is incomplete given the tool's complexity (9 parameters, multiple modes). It fails to explain mode interactions, parameter dependencies, or how to use the tool effectively, leaving significant gaps for an AI agent.

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 0% schema description coverage, the description must compensate. It only explains the screenshot_meta parameter, leaving the other eight parameters (key, keys, action, x, y, button, window) completely unexplained. The agent lacks needed context for correct parameter usage.

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 that the tool sends keyboard or mouse input via ydotool. It specifies the resource and action, but does not explicitly differentiate from sibling tools like 'set_text' or 'interact', leaving some ambiguity for agents.

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 a specific usage scenario (mouse mode with screenshot metadata), which offers some guidance. However, it lacks general instructions on when to use this tool versus alternatives, and does not cover other modes or prerequisites.

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