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

Annotations only say readOnlyHint=false, openWorldHint=true, and destructiveHint=false; the description carries the behavioral burden and does exceptionally well. It discloses the side effects (upload and print start), the protocol-specific auth and network behavior, the dry_run escape hatch, and the guarantee that credentials are never logged or echoed. No contradiction with 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?

The description is front-loaded with the primary use case, then packs relevant protocol details, auth requirements, and the dry_run behavior into a dense but efficient paragraph. Every sentence contributes operational information; there is no filler or redundant restating of the title.

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's 10 parameters, three protocols with distinct auth models, and side-effecting behavior, the description covers what an agent needs: when to use it, what each protocol requires, how to avoid side effects, and how to validate connectivity. Since an output schema exists, the return format is not the description's responsibility.

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?

Input schema covers 90% of parameters with good descriptions, so the baseline is 3. The description adds meaningful value by explaining protocol-specific requirements, such as when serial is required for bambu-lan, which parameters matter for each protocol, and what dry_run does. It does not restate what the schema already says.

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?

States a specific verb/resource: upload a .gcode file to a real network printer and, by default, start the print. It also references the export tool output format, making the purpose concrete and distinct from the CAD/analysis-focused sibling 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?

Explicitly opens with 'Use this when you need to upload a .gcode file...' and explains the dry_run mode for connectivity/auth validation. It names all supported protocols and their prerequisites, giving clear context, though it does not explicitly state when not to use the tool since no close printer sibling exists.

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