simscale_upload_file

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

Annotations already indicate non-readOnly, non-idempotent, non-destructive. The description adds valuable context about the file root, visible input requirement, and mandatory confirmation, without contradicting the annotations.

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?

Two sentences, front-loaded with the action, and no redundant wording. Every word earns its place.

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 description covers the core action and key constraints, but with a complex target object and no output schema, it leaves gaps on how to choose among target properties (test_id, role+name, label) and what the result looks like.

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 coverage is only 33% (target has a description). The description adds meaning for file_path (from SIMSCALE_FILE_ROOT) and confirm_upload (safety confirmation), but does not elaborate on target property selection, leaving the nested object partially unexplained.

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 a specific verb ('Upload') and resource ('CAD or other local file'), plus the source ('from SIMSCALE_FILE_ROOT') and destination ('through a visible file input'). This distinguishes it from siblings like simscale_click or simscale_fill.

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 doesn't explicitly mention alternatives, but it provides clear context: upload from a specific root via a visible input, and requires confirm_upload=true. Since no sibling tool handles uploads, this is sufficient guidance.

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