Fill form

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

Annotations already indicate destructiveHint=true, so the description carries a lower burden. However, it adds no behavioral context beyond the name—e.g., whether fields are validated, what happens when a field is missing, or if the form submits automatically. This is insufficient for a mutation tool with side effects.

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?

At 4 words, the description is extremely short but under-specified for a tool with complex nested parameters. It sacrifices necessary information for brevity, making it more deficient than concise.

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 the tool's complexity (2 parameters, one a nested array of objects with 4 fields) and absence of an output schema, the description must provide more context. It fails to mention return values, error handling, or prerequisites (e.g., form must be visible). The description is far from 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 description coverage is 0%, requiring the description to compensate for parameter meanings. The description offers no details about the 'fields' array, its required properties (name, target, type, value), or how to specify values. The agent must infer semantics from the schema alone, which lacks descriptions.

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 'Fill multiple form fields' clearly states the action (fill) and resource (form fields), implying batch operation. However, it does not differentiate from sibling tools like browser_type (single field) or browser_select_option, and the title 'Fill form' is redundant.

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 is provided on when to use this tool versus alternatives such as browser_type for individual fields or browser_select_option for dropdowns. The description lacks any context for appropriate usage.

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