veil_type

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

No annotations provided and description omits behavioral traits: what happens if no element is focused, whether it clears existing text, how special characters are handled, or if it is blocking/asynchronous.

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?

Single sentence, no wasted words. However, it sacrifices necessary detail for brevity.

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 simple one-parameter tool with no output schema, the description is incomplete: lacks usage context, behavioral notes, and parameter semantics. It serves only as a minimal header.

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?

With 0% schema description coverage, the description must compensate but only mentions 'text' without explaining format, allowed characters, or behavior. It adds no value beyond the schema's type 'string'.

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 'Type text into the currently focused element' clearly identifies the verb (type) and resource (focused element). It distinguishes from siblings like veil_click and veil_fill, but does not clarify its difference from veil_text, which is a near-sibling.

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 alternatives (e.g., veil_fill for form fields, veil_press for keys), nor any prerequisites or context requirements specified.

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