fill_form

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

With no annotations, the description must disclose behavioral traits. It does not mention side effects, waiting behavior, error handling, or what happens upon submission. Only a parameter example is given, which is insufficient for a mutation tool.

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 extremely concise: two sentences and an example. Every part serves a purpose, with no redundancy or unnecessary 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 that there is an output schema (unspecified) and the tool involves form interaction with potential errors, the description omits important details like return value, error states, and page interaction guarantees. It is too minimal for the task's complexity.

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%, so the description partially compensates by explaining the structure of 'fields' array with examples of 'ref' and 'selector' keys. However, it does not clarify all possible properties (since additionalProperties is true) and does not elaborate on 'submit_ref' beyond its existence.

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 'Fill multiple fields then optionally submit,' with an example showing field objects, making the verb and resource obvious. It distinguishes from siblings like 'fill' (single field) and 'smart_fill' (AI-assisted) through the explicit mention of multiple fields.

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 vs alternatives such as 'fill', 'type_text', or 'smart_fill'. There is no mention of prerequisites (e.g., form must be visible) or conditions for submission.

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