type_text

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

With no annotations, the description reveals the clipboard-based implementation for Unicode, implying potential clipboard content overwrite. This is sufficient behavioral disclosure for a simple tool, though not exhaustive.

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 two sentences, concise and front-loaded. Every sentence earns its place without excess.

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?

Given the simplicity (one param, no output schema), the description explains the Unicode mechanism adequately. Slight improvement could mention reliance on focus state.

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 100% for the single parameter 'text', but the tool description adds no additional meaning beyond the schema's basic description of the parameter content.

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 clearly states the tool types text at the current focus position, using a specific verb (Gõ text) and resource (vị trí focus hiện tại). It naturally distinguishes from siblings like key_press and set_clipboard.

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 provides a mechanism hint (clipboard + Ctrl+V for Unicode) but does not explicitly state when to use this tool versus alternatives like key_press or set_clipboard. No when-not scenarios are given.

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