ie_upload

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

With no annotations, the description should fully disclose behavior. It mentions 'sending a local file path' but does not explain whether this triggers a file selection dialog or directly sets the input value, nor does it state side effects or requirements (e.g., file existence). The behavior remains ambiguous.

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 a single short sentence, which is concise but lacks essential detail. It could be expanded to cover parameters and usage context without being 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?

Given the tool has 4 parameters (3 required) and no output schema, the description is insufficient. It fails to explain how to specify the file input element (by/value/frame) and what the tool does beyond setting a path. The definition is incomplete for effective use.

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 input schema has 4 parameters with only 25% description coverage (only 'path' is described). The tool description adds no additional meaning for the parameters 'by', 'value', or 'frame', leaving them unexplained. This is a critical gap for a required parameter (by, value, path).

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 identifies the tool's purpose: setting a file input by providing a local file path. It effectively distinguishes from sibling tools like 'ie_fill' (for text inputs) and 'ie_click' (for actions). The verb 'set' is specific and the resource is well-defined.

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 file upload scenarios, but lacks explicit guidance on when to use versus alternatives like 'ie_fill' or prerequisites (e.g., the file input must exist and be visible). No when-not or alternative tool suggestions are provided.

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