start_print

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

No annotations are provided, so the description carries the full burden. It discloses a write operation ('Start printing') but does not specify other behavioral traits such as whether the printer must be idle, what happens if the file is not found, or if the printing starts immediately. The model warning in the schema is not in the description.

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 two sentences with no unnecessary words. It efficiently conveys the tool's action and its alias relationship. Every sentence adds value.

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 5 parameters (2 required), no output schema, and no annotations, the description provides the core action but omits details about return values, error states, or progress feedback. The high schema coverage partially compensates, but the description could be more complete.

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 the schema already documents all parameters. The description adds meaningful context beyond the schema by clarifying that the file must already be on the printer ('already on the Bambu Lab printer'), which is not obvious from the 'filename' parameter alone.

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 action ('Start printing'), the resource ('G-code file already on the Bambu Lab printer'), and distinguishes itself from siblings by noting it is an alias of start_print_job. This provides a specific verb+resource and differentiates from similar tools.

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 mentions it is an alias but does not explicitly state when to use this tool vs start_print_job or other printing tools. There is no guidance on prerequisites or when not to use it. The schema description for bambu_model warns about damaging the printer, which is implicit guidance, but no explicit usage instructions.

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