type_text

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

With no annotations, the description fully discloses the dual method (xdotool vs clipboard), the rationale for the clipboard fallback (toolkit compatibility), and the fallback failure behavior (isError if xclip missing). Also documents the return format.

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 well-structured with the main purpose front-loaded. Slightly verbose in explaining the unicode workaround, but the detail is necessary for transparency.

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?

Good coverage of core behavior and failure modes, but lack of detail on observe/instance/settle_ms parameters leaves a gap. Since there is no output schema, the return format is described, which is helpful.

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 coverage is 0%, yet only 'text' is explained (typed input). The other three parameters (observe, instance, settle_ms) are merely referenced with a direction to 'see click()', providing no independent semantics. This is insufficient.

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 'Type into the focused field — unicode-safe', which clearly indicates the action (type) and resource (focused field). It distinguishes from siblings like click or press_keys, though not explicitly naming them.

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?

Explicitly instructs to click the field first to focus it. Provides context on when the clipboard fallback is used (non-ASCII characters) and failure conditions (missing xclip). Does not list when to avoid this tool in favor of alternatives.

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