type_text

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

No annotations are provided, so the description carries the full behavioral burden. It hints at a precondition ("currently focused element") but never says what happens if no element is focused, whether existing content is replaced or appended, or that accessibility/input permissions may be required. For an input-injection tool this is a substantial gap.

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 sentence, front-loaded with the verb and target, with no wasted phrasing. It is efficient, though its brevity is achieved by omission rather than precision.

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 a focus-dependent input action, the description should cover failure modes and preconditions. It covers only the happy path, so an agent cannot predict behavior when focus is absent or when `background` is used with a non-native window.

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 50%: the optional `background` parameter is documented in the schema, but `text` has no schema description and the description only vaguely says "a string of text." It adds essentially nothing beyond the field names, leaving the foreground/background tradeoff (native apps only) unexplained in the description.

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?

It states a specific verb ("Type") and resource ("a string of text") plus the target ("currently focused element"), which is enough to understand the operation. It does not distinguish itself from near-siblings such as ax_set_value, write_clipboard, or key_combo, which an agent must disambiguate on its own.

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 gives no when-to-use guidance and never mentions alternatives. It does not explain when to prefer typing over ax_set_value or clipboard-based insertion, nor what to do if nothing is focused. With ~30 sibling tools, this omission is significant.

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