project.open

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

Annotations already convey destructive/read-only/idempotent hints, so the description only needs to add extra behavioral context. It does so by disclosing the next-tick execution, default transaction commit, and dirty-project saving behavior. There is no contradiction with the annotations.

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 two tight sentences with no filler. It front-loads the primary action and then states the important default side effects, which is an efficient structure for an agent-facing tool definition.

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 having an output schema, the tool has five parameters and zero schema description coverage. The description fails to explain key optional parameters such as load_ui, use_scripts, and save_current_as, and it does not guide the agent toward or away from sibling project tools. This is not fully complete for correct invocation.

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?

Schema description coverage is 0%, so the description must carry the parameter-meaning burden. It only explains path ('absolute .blend path') and partially touches save_current via the default-save behavior. load_ui, use_scripts, and save_current_as are left undocumented in both the schema and the description.

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 states a specific verb ('Open'), a specific resource ('existing absolute .blend path'), and a concrete scheduling detail ('on the next main-thread tick'). This clearly distinguishes project.open from siblings like project.reload or project.save and is not a tautology.

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: to open an existing .blend file while committing the current transaction and saving the dirty project. However, it does not explicitly name alternatives, exclusions, or conditions under which another sibling tool such as project.reload should be used instead.

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