gui_project_state

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

No annotations provided, so description carries full burden. It discloses what the tool returns (source file, presets, overrides) and implies it is read-only. Slightly less transparent about the exact format or whether it blocks, but adequate for a simple state query.

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 wasted words. The first sentence defines the tool's output, the second provides critical usage guidance. Front-loaded with essential information.

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?

Despite no output schema, the description gives a good sense of return values (source file, presets, overrides). For a zero-parameter, read-only tool, this is sufficient. Could mention if the output is flat or structured, but not strictly necessary.

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 schema coverage is 100% by default. Description does not need to add parameter info; baseline 4 applies. No additional meaning needed.

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?

Description clearly states it returns the current GUI state of OrcaSlicer: source file, presets, and overrides. The verb 'check' implies a read operation, and the resource is clearly the GUI project state. Distinguishes from sibling tools like 'slice_model' or 'printer_status' by focusing on the user's open project.

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?

Explicitly states when to use: 'ALWAYS check this before choosing slicing presets yourself' and provides a clear rule: 'if the user has the part open, their settings win.' This directly guides the agent on precedence.

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