status

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 states 'Read', implying a non-destructive operation, and lists the data fields. However, it does not disclose error behavior (e.g., what happens if the printer is unreachable) or any other behavioral details beyond the read nature. For a simple status tool, this is adequate but not rich. A score of 3 reflects the minimum viable transparency.

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 that states the action and resource first, then lists the specific data points. Every word earns its place, and there is no redundancy. The structure is optimal for quick agent comprehension.

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?

With no output schema, the description is responsible for explaining the return value. It lists all key fields (gcode_state, progress %, remaining minutes, layer, job name) in a clear manner, providing enough detail for an agent to understand what it will receive. The tool is simple (no parameters, read-only), so this is 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?

The tool has zero parameters, and the schema is empty. Per the rubric, a baseline of 4 is appropriate when there are no parameters. The description does not need to add parameter semantics, and there is nothing to explain. The description's mention of the return fields is sufficient context.

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 ('Read') and the resource ('Bambu LAN print state'), then enumerates the specific fields returned (gcode_state, progress %, remaining minutes, layer, job name). This is specific and distinct from sibling action tools like stop, pause, and resume, which perform state changes rather than reading state.

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 context is clear: this is a read operation for current print state, making it obvious when to call it (whenever the agent needs current print status). It does not explicitly name alternatives or state when not to use it, but given the sibling set (actions vs. this read), the usage is unambiguous. A score of 4 reflects clear context without explicit exclusion guidance.

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