Connector info

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description is consistent with those and adds useful behavioral context about detecting first-use setup and the required follow-up flow, though it does not elaborate on error behavior or response details.

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?

Two compact sentences front-load what the tool returns and follow with the key session-start workflow. Every sentence carries useful information, and there is no repetition beyond the brief read-only confirmation.

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 zero-parameter, read-only info tool with no output schema, the description sufficiently explains the returned status fields and the conditional setup workflow. An agent has enough context to call it first and know what to do if setup_needed is true.

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, so there is no parameter semantics to clarify. The baseline for a no-parameter tool is 4.

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 and resource: return the connector's status. It enumerates the status contents (setup_needed, saved defaults, Bambu Studio and preset paths, output folder, printer configured) and connects to the sibling setup_defaults, so an agent can distinguish it from tools like printer_status or list_presets.

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?

It gives clear usage guidance: call it first in a session, then if setup_needed is true ask the user for printer/build plate/filament and call setup_defaults. The next-step routing is explicit, though it does not state when not to use the tool.

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