touchpad

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

With no annotations, the description carries the full burden. It usefully discloses a real behavioral limitation — coordinates are sent but not delivered because touch mapping is unknown — which an agent must know. It does not disclose whether the click has destructive side effects, what the returned result is, or how duration_ms and snapshot_after_ms affect behavior.

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?

Two short sentences with the action front-loaded and the important caveat second. No wasted words, though the second sentence is cryptic and could be phrased more clearly.

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?

No annotations, no output schema, and four undocumented parameters. The description covers the action and one caveat but leaves parameter meaning and behavioral consequences almost entirely to inference, which is insufficient for a mutation-style interaction 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 0% across 4 parameters. The description only gestures at the x/y coordinates ('Coordinates are sent') without format, range, or meaning, and says nothing about duration_ms or snapshot_after_ms, leaving two parameters entirely unexplained beyond their defaults.

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?

States a specific verb and resource ('Click the touchpad'), so the basic action is unambiguous. However, it never distinguishes itself from sibling tools like press, hold, stick, or trigger, which likely operate on the same touch surface, leaving the agent to guess which to use.

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?

There is no guidance on when this tool should be used versus press/hold/trigger, nor any stated preconditions. The caveat that coordinates are 'not yet delivered' hints the tool may be unreliable, but this is not framed as an explicit usage rule.

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