safari_type

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

Mentions event firing (input/change), which is good. But no info on append vs replace, behavior on multiple matches, or required page state. Without annotations, description carries burden but is incomplete.

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, very concise. Lacks structure but effective for core action. Slightly too minimal.

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?

Empty schema contradicts description implying required parameters (selector, value). No output schema info. Incomplete for a tool that likely needs parameters.

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 no parameters (100% coverage), but description doesn't explain how to provide CSS selector and value. Baseline 4 is reduced because description fails to compensate for missing schema details.

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?

Description clearly states it sets the value of input/textarea using CSS selector and fires events. Distinguishes from siblings like safari_click or safari_fill_form.

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 vs alternatives like safari_fill_form or chrome_type. Implies use for single field input but lacks explicit context.

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