sync_with_bambu_studio

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

With no annotations, the description carries the full behavioral burden and does so well. It discloses automatic synchronization timing and clearly warns that force=True discards unsaved changes by taking the app's version.

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?

The description is compact and front-loaded with the core action and trigger condition. Every clause adds useful information about automatic behavior or force semantics without repetition.

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 one-parameter synchronization tool with no annotations or output schema, the description provides enough context to call it correctly. It covers purpose, timing, automatic behavior, and the destructive consequence of force=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?

Although schema coverage is 0%, the description fully explains the only parameter: force=True overrides unsaved changes and takes the app's version, causing those changes to be lost. This adds essential meaning beyond the bare boolean schema.

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?

States the specific action (re-read the project file) and the exact situation (after manual changes in Bambu Studio were saved to the same file). This clearly distinguishes it from sibling project-opening and saving tools by focusing on synchronization of an externally edited file.

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?

Explains when to use it: after editing the file by hand in Bambu Studio and saving. It also describes automatic synchronization when there are no unsaved changes and the special case requiring force=True when unsaved changes exist.

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