upload_gcode

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

With no annotations, the description carries the full burden. It correctly conveys that the tool does not start printing, but it fails to disclose any side effects, such as whether existing files are overwritten, required permissions, or file size limits.

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: a single sentence plus a clarifying note. Every word serves a purpose, and it is front-loaded with the core action.

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 is somewhat complete for a simple file upload, but given the 3 parameters, lack of parameter explanations, and no behavioral details beyond the not-starting-printing disclaimer, the agent may be misled about required inputs and behavior. An output schema exists, which reduces the need to describe return values.

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 0% description coverage, and the tool description adds no information about the parameters ('gcode_path', 'host', 'remote_name'). The parameter names are somewhat self-explanatory, but the agent receives no guidance on what 'host' or 'remote_name' are or how to use them.

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 the verb 'Upload' and the resource 'G-code file to the printer,' making the tool's purpose specific and unambiguous. It explicitly distinguishes itself from 'start_print' by noting that it does not start printing.

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 provides explicit guidance on when not to use this tool ('Does NOT start printing') and directs to an alternative ('use start_print for that'). However, it does not offer guidance relative to other siblings like 'analyze_gcode' or 'printer_files.'

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