bambu_status

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

With no annotations, the description must carry behavioral disclosure. It does say what information is returned (which is genuinely useful given there is no output schema), but it never states that the call is read-only/without side effects, nor what happens when Bambu Studio is not installed.

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 tight clause that front-loads the resource (installation location) followed by the remaining reported fields. Nothing extraneous, though it reads as a fragment rather than a sentence.

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 field enumeration is doing real work, but it omits the failure mode (not installed / not running) and the shape of values such as version strings or project paths. Adequate for a trivial zero-param tool, but not 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?

Zero parameters, so there is nothing for the description to disambiguate. The baseline of 4 applies; no parameter semantics are required or missing.

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 names the specific resource and enumerates what the status covers: install location, version, running state, and current project. It is clearly distinguishable from name alone, though it lacks an explicit verb and never differentiates itself from siblings like printer_status or sync_with_bambu_studio.

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 guidance on when to call this versus printer_status or open_in_bambu_studio, and no prerequisites such as 'Bambu Studio must be installed'. The usage is only implied by the name and the field list.

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