type_text

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

Annotations indicate mutability (readOnlyHint=false) and non-destructiveness (destructiveHint=false). Description adds important details: uses WM_CHAR for background typing, includes interval, and demonstrates safe mutation. No contradictions.

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?

Two compact paragraphs with clear heading for background targeting. Every sentence adds value, no verbosity.

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 output schema specifying return JSON, description covers core behavior. Could mention error cases but overall sufficient for a simple typing tool.

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 has detailed parameter descriptions (e.g., hwnd, text, interval). Description adds value by unifying targeting concepts but does not elaborate on parameter meanings beyond schema. Baseline 3 is appropriate given high schema coverage.

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?

Clearly states 'Type a string of text into the currently focused window/control.' The verb 'type' and resource 'text into window/control' are specific. It also distinguishes from sibling like win_set_control_text by noting its higher reliability for edit controls.

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 explains background targeting via hwnd or window_title and advises using win_set_control_text for edit controls. Provides clear context but doesn't exhaustively cover all when-to-use scenarios.

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