Desktop Type

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

With no annotations, the description carries the full burden, yet it doesn't say whether existing text is replaced or appended, whether the field is focused automatically, or whether window focus/heading is required. The 'headed' parameter's behavioral effect is never mentioned.

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?

It's a single efficient sentence with no filler, but that brevity comes at the cost of the detail an agent needs; the sentence is terse rather than front-loaded with actionable context.

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?

An output schema exists so return values need not be described, but for a mutation tool with zero annotation coverage and 0% parameter documentation, the description should explain the ref acquisition path and the headed flag. It falls well short.

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 three parameters. The description hints that ref_id is a 'qualified ref' but never explains the ref format or how to obtain one (e.g., from desktop_find or desktop_snapshot), and leaves 'headed' and 'text' entirely unexplained.

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 states a specific verb and resource — 'insert text into a text field target' — which is meaningfully distinct from siblings like desktop_press or desktop_click. It does not explicitly name an alternative, but the action is unambiguous.

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 to use this versus desktop_press (keystrokes), desktop_action, or desktop_click to focus a field first. No preconditions such as requiring the target window to be focused are stated.

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