browser_fill_form

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

No annotations are present, so the description must cover behavioral traits. It only mentions optional 'submit?' and 'clear?' without explaining their effects, and omits details on field validation, error handling, or session requirements.

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?

The description is very short and front-loaded, but could be slightly more structured (e.g., bullet points for field properties). It is not 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?

The tool has two parameters and an output schema exists (not shown), so return value explanation is unneeded. However, the description lacks prerequisites (e.g., active session) and does not clarify the role of 'session_id'. It feels incomplete for a form-filling operation.

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?

The description adds structure for the 'fields' parameter (ref, value, submit?, clear?) but does not define these terms or explain the 'session_id' parameter. With 0% schema coverage, more detail was needed.

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 clearly states the verb ('Fill') and resource ('multiple fields') with a concise structure hint, distinguishing it from single-field tools like browser_type.

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?

The description implies usage for bulk field filling but provides no when-not-to-use instructions or comparisons with sibling tools (e.g., browser_type for single fields).

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