zen_type

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

With no annotations, description carries full burden but only states 'type text'. Does not disclose if it simulates keystrokes, triggers events, requires focus, or waits for element existence. Behavioral details are minimal.

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?

Description is extremely concise: one sentence action followed by a clear bullet list of arguments. Every word earns its place, no fluff.

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?

No output schema or annotations; description only covers basic usage. Leaves out return value, error handling, prerequisites (element must exist), and interaction with page state. Incomplete for a typing tool with 4 params.

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?

Description adds meaning to each parameter beyond schema types: 'CSS selector', 'Text to type', 'clear existing text', 'optional tab'. Schema has 0% coverage, so description compensates partially. Missing details like key combinations or format constraints.

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 text into an input field' which is a specific verb+resource. It distinguishes from siblings like zen_fill (form filling) and zen_set_editable_content (content setting) by focusing on keystroke typing. Parameter list reinforces the action.

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?

No guidance on when to use this tool versus siblings (e.g., zen_fill, zen_click). No mention of contexts where typing is preferred over other input methods. Agent must infer from name and args.

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