fulu_bambu_network_rpc

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

With no annotations, the description carries the full burden and does well: it discloses the default read-only posture, the mutating-method opt-in flag, the refusal class, and the reason (bypassing the print safety gate). It omits return/error behavior and timeout implications, but the safety semantics are unusually well communicated.

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?

Three sentences, front-loaded with what the tool is, then the gating rules, then the refusal and alternative. Every sentence carries information; no filler or repeated schema text.

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 6-parameter passthrough with a free-form payload and no output schema, the description covers the safety model well but does not describe what an RPC call returns, how failures surface, or how to choose among the many allowed bridge methods beyond the schema's examples. Adequate but with clear gaps.

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 method, payload, timeout_ms, bambu_model, bridge_command and allow_mutating_method. The description adds one genuinely useful nuance — that allow_mutating_method never enables print, printer-message or unknown methods — but otherwise restates schema-level guidance, fitting the baseline 3.

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?

Names a specific resource (FULU BambuNetwork bridge RPC) used for diagnostics and development, and distinguishes its scope from print-oriented siblings by explicitly excluding raw print methods. The verb is generic (a passthrough RPC), so it is not a perfect verb+resource pair, but an agent can tell it apart from print_3mf and check_fulu_orca_setup.

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?

Gives explicit conditional routing: read-only methods allowed by default, agent/session setup methods require allow_mutating_method=true, and print/message/file-transfer/unknown methods are refused. It also names the correct alternative (print_3mf) for checked printing. It stops short of saying which diagnostic scenarios warrant calling this tool.

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