browser_fill

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

Discloses the method ('CDP Input.insertText') and mentions clearing the field, but does not elaborate on side effects (e.g., event triggering, hidden inputs). Annotations are absent, so the description carries full burden but leaves gaps.

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 of 14 words, front-loaded with key action. Efficient but could benefit from a brief usage note without becoming verbose.

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, so description should hint at return value or success/failure. Lacks details on error handling, focus requirements, or what happens after fill. Adequate for a simple tool but not fully complete.

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 covers both parameters with descriptions. Description adds no extra meaning beyond schema – it reiterates the action but does not clarify formatting, escape rules, or behavior for special characters.

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 the action: 'Clear and fill an input field with text'. It specifies the resource ('input field') and the verb ('fill'), and distinguishes from sibling tools like browser_click or browser_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?

No guidance on when to use this tool versus alternatives like browser_eval or browser_click for filling forms. No mention of prerequisites (e.g., page must be loaded, input must be visible) or when not to use.

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