bambu_network_bridge_status

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

No annotations are provided, so the description carries the full behavioral burden, yet it does not disclose that the tool can start a bridge process/execute a command (connect=true, bridge_command), that per-call command overrides require MCP_ALLOW_EXECUTABLE_ARG=1, or what a successful/failed probe reports. Only the vague verb 'probe' hints at side effects.

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?

A single, front-loaded sentence with no padding. It is efficient, though dense with product-specific jargon that slightly raises interpretation cost.

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 tool with six optional parameters, no annotations, and no output schema that can launch an external bridge process, the description omits the most decision-relevant facts: side effects of connect, return/result shape, failure modes, and prerequisites. What an agent needs to call it confidently is largely missing.

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 all six parameters (connect, user_info, timeout_ms, country_code, bridge_command, bambu_network_config_dir) are already fully documented by the schema. The description adds no syntax, default, or interaction detail beyond it, which is the expected baseline of 3 when the schema does the work.

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 states a specific verb pair (inspect/probe) and resource (the FULU OrcaSlicer-bambulab BambuNetwork bridge runtime), with an additional scope note about cloud and restored BambuNetwork printing. An agent can tell this apart from an ordinary network call, but the description never names the sibling tools (bambu_network_call, print_3mf_bambu_network) it should be preferred over.

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?

There is no when-to-use guidance at all: no statement of when to inspect versus when to actually invoke bambu_network_call or print_3mf_bambu_network, and no hint about when the connect probe is appropriate versus a plain status read. Usage is only implied by the word 'probe'.

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