upload_file

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and idempotentHint=false, so the framing is not invisible. But the description adds nothing beyond that: it does not mention that setting print=true will start a physical print job, that bambu_native never starts printing, that bambu_model is required for printable uploads, or that credentials come from the environment. For a 12-parameter mutation tool, that is a substantial gap.

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?

It is a single front-loaded sentence with no wasted words, so it is structurally clean. However, that brevity is under-specification rather than efficiency: the one sentence leaves out the print-triggering behavior and the transport choice that dominate this tool's use.

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?

With 12 parameters, a required model argument for printable files, a destructive-adjacent print flag, and two transport modes, this definition is far too thin. There is no output schema, so the description should at minimum state what the upload returns and how print versus upload-only differs. An agent calling it correctly would have to rely entirely on the schema descriptions.

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 100%, so every parameter, including the host/token/serial defaults, the connection_mode enum semantics, and the X2D-specific plate and preset fields, is already documented in the schema. The description contributes no additional meaning about parameters. A baseline of 3 is appropriate when the schema carries that load.

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 states a clear verb and resource: 'Upload a local file to the Bambu Lab printer'. An agent can immediately tell this transfers a file rather than printing, inspecting, or deleting. It does nothing to distinguish the tool from siblings such as upload_gcode or bambu_connect_import_file, which is why it falls short of a 5.

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?

There is no when-to-use or when-not-to-use guidance, and no alternative is named. The description does not explain how this differs from upload_gcode or bambu_connect_import_file, nor when the 'print' flag or 'connection_mode' should be chosen. The agent is left to infer selection entirely from the schema.

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