get_project

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

With no annotations, the description carries the full burden; it does disclose a genuinely useful behavioral trait — that the project is re-read if it was saved in Bambu Studio in the meantime, which signals freshness/consistency semantics. However it never states read-only safety, whether an error occurs when no project is open, or anything about payload size/cost.

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 sentences, no filler, and the core content is front-loaded. The first sentence is a dense comma-separated list that is slightly cryptic (bare 'printer, process'), but nothing is wasted.

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 and no annotations, the description is the only documentation, and it partially compensates by enumerating returned fields and stating the re-read behavior. It still omits the read-only guarantee, failure modes when no project is loaded, and how large/nested the object payload is.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The enumerated field list in the description is effectively return-value documentation, which the schema does not provide.

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 is a noun-phrase inventory of what the project object contains (printer, process, filament slots, plates, objects, overrides, warnings) rather than a verb+resource statement; combined with the name get_project the intent is inferable, but the agent must do the work. It does nothing to distinguish this state reader from siblings like bambu_status, list_printers, or get_setting.

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, no statement of prerequisites (e.g. must a project be open), and no routing to alternatives such as bambu_status or get_setting. The only conditional sentence is about re-reading, which is behavioral rather than usage guidance.

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