Open project

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

Annotations declare destructiveHint=true and non-idempotent, but the description adds context they don't cover: the current project is closed, unsaved changes are lost unless handled, opening can take minutes, and Archicad may surface dialogs (e.g. missing libraries). It even documents the return shape.

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?

Three dense sentences with zero padding, front-loading the destructive close-current-project consequence before the recovery options and the long-running warning.

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 destructive, blocking, dialog-prone operation with no output schema, the description supplies the side effects, the mandatory parameter decision, the path-type semantics, and the return shape — nothing material is missing.

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 100%, so the baseline is 3, but the description adds value the schema lacks: the file-type-to-behavior mapping (archive, template → untitled, backup) attached to `path`, plus reinforcement of the saveFirst/discardChanges mutual exclusion.

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 a specific verb (opens) and resource (a project file), enumerates the supported extensions (.pln, .pla, .tpl, .bpn), and clarifies the side effect of closing the current project. An agent can distinguish it from new_project, save_project_as, and close_project without opening any schema.

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 names when-not (BIMcloud/Teamwork projects cannot be opened by path) and routes the agent to the alternative (use save_project_as first for untitled projects). It also states the mandatory decision between saveFirst and discardChanges.

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