start_print

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only that the print starts from an existing file and that this is a compatibility alias. It says nothing about what is affected (current job, AMS state), typical duration, or what happens if a print is already running.

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 short sentences, purpose front-loaded, with the alias note in the trailing position where it belongs. No filler or restatement of the tool name.

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?

For a five-parameter mutation tool with no output schema, the description plus fully documented schema and annotations cover the essentials. Remaining gaps are behavioral (preemption of a running job, return value), which are minor given the rich annotations.

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 100%, including a strongly worded bambu_model description warning of hardware damage from a wrong model, so the schema carries parameter meaning. The description adds no extra semantics about filename resolution, host override, or token/serial defaults. Baseline 3 applies.

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?

Concrete verb plus resource plus precondition: "Start printing a G-code file already on the Bambu Lab printer." It also discloses that it is an alias of start_print_job, which lets an agent tell it apart from siblings like print_3mf and upload_gcode. It stops short of explicitly stating it produces the identical effect as that sibling.

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 phrase "file already on the printer" implies the file must be uploaded first, which points indirectly at upload_gcode/list_printer_files. However, there is no explicit when-to-use guidance, no statement of which sibling to prefer, and no prerequisites such as the printer needing to be idle or connected.

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