real_type

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

Discloses key behaviors: uses real OS events (isTrusted), brings Floorp to foreground, aborts on verification failure, Windows-only. These add value beyond annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true). No contradiction.

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?

Three sentences, front-loaded with purpose and usage guidelines. Every sentence provides necessary information without redundancy.

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?

For a tool with one parameter and no output schema, the description covers purpose, usage, prerequisites, failure behavior, and platform limitation. Complete and self-contained.

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 already describes the single `text` parameter with maxLength and description. Description does not add extra meaning beyond what the schema provides, so baseline 3 is appropriate.

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 the tool types text using real OS keyboard events (isTrusted) into Floorp's focused element. Distinguishes from sibling `type_text` by noting it works for React/rich editors where `type_text` fails.

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 says when to use (React/rich editors where `type_text` fails), prerequisites (Floorp running, Windows only), and steps (focus field with `click`). Also notes abort behavior if foreground verification fails.

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