safari_fill

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

No annotations provided, so description carries full burden. Discloses that it replaces existing content, handles complex editors automatically, and warns that refs expire. 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 concise sentences that front-load key information: what it does, when to use alternatives, and a critical ref warning. No wasted words.

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?

Given simple input action with 3 parameters (1 required) and no output schema, description covers all essential aspects: purpose, usage context, behavioral notes, and parameter handling. Complete for reliable agent invocation.

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?

Input schema has 100% coverage, so baseline is 3. Description adds important context about ref expiration and that selector is optional, but does not elaborate further on value format or selector specificity. Still adds meaningful guidance beyond schema.

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 it fills or replaces values in inputs, textareas, selects, and contenteditables, handling multiple frameworks. Explicitly distinguishes from sibling tools like safari_replace_editor and safari_type_text.

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?

Provides explicit guidance on when to use this tool (setting a value) versus alternatives (code editors: safari_replace_editor; typing: safari_type_text). Includes critical note about refreshing refs after snapshots.

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