exit_sculpt_mode

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the mode change but does not mention preconditions (e.g., being in sculpt mode), side effects (e.g., whether sculpt data is preserved), or error behavior if called when not in sculpt mode. This is a significant gap for a state-changing tool.

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 a single, front-loaded sentence with no wasted words. It conveys the exact action and result without any redundancy.

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 mode switch with no output schema, the description covers the core action and outcome. It is mostly complete, though it could mention whether it requires an active object or if undo history is affected. These are minor gaps given the tool's simplicity.

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?

With zero parameters, the baseline is 4 as per guidelines. The description does not need to explain parameters, and no additional semantic info is required.

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 clearly states the action (exit sculpt mode) and the resulting state (return to object mode), using a specific verb and resource. It is easily distinguished from the sibling tool enter_sculpt_mode, which performs the inverse operation.

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?

The description implies when to use the tool (when in sculpt mode and wanting to return to object mode) but does not explicitly mention the alternative enter_sculpt_mode or any exclusions. It provides minimal guidance beyond the obvious context.

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