input.humanize

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

With no annotations, the description carries the full disclosure burden. It does not say whether the gesture is a click, hover, or movement, whether it is reversible, whether it requires an active page/session, or why it must be 'outside the page map' — only that one gesture is dispatched.

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?

A single front-loaded sentence with no filler. It is terse rather than padded, though the terseness comes at the cost of clarity.

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?

With no annotations, no output schema, and an empty parameter object, the description is the only source of behavior — and it leaves the gesture type, coordinate source, and effect unspecified. Inadequate for an input-dispatch tool in a browser automation surface.

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 schema declares zero parameters, which normally earns a baseline 4, but the description explicitly requires 'a coordinate' that appears nowhere in the schema. That mismatch creates ambiguity rather than adding meaning, so it lands below baseline.

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 verb 'Dispatch' and object 'gesture' are present, but 'humanized gesture' is undefined jargon and 'outside the page map' is opaque — an agent cannot tell whether this moves the pointer, clicks, or types. It is distinguishable from siblings only by name, not by stated effect.

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?

No indication of when to prefer this over click, press_and_hold, interact, or other input siblings, and no prerequisites or conditions given. The phrase 'outside the page map' hints at a niche, but the trigger is never stated.

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