open_revit_model

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

No annotations, so the description carries the full load; it earns credit for disclosing the significant side effect that the managed instance and its bridge are started automatically if needed. It does not say whether the call blocks until the model opens or returns immediately for later polling, nor what happens on incompatible/missing files, both of which matter for a process-spawning mutation.

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 short sentences, front-loaded with the action and target, then the automatic-provisioning note, then the exclusion. Nothing is redundant or padded.

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?

There is no output schema and no annotations, and the description never addresses what the call returns or how to learn whether the open succeeded — a real gap given that get_revit_operation_result exists as a sibling. It is otherwise adequate for a single-parameter tool.

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?

Only one parameter with 100% schema description coverage, so the schema already defines the path and its Revit 2020 compatibility requirement. The description repeats 'absolute path' without adding format examples, expected failure modes, or other meaning beyond the schema.

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?

A specific verb ('Open') plus resource ('existing RVT or RFA') scoped to a named environment ('separate managed Revit 2020 instance'). The closing sentence rules out interaction with the user's other Revit instances, which cleanly separates this tool from the status/dialog siblings that operate on the automation session.

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?

It gives clear conditions for use: an existing absolute RVT/RFA path, target Revit 2020, managed instance. It also states a negative condition ('Does not connect to the user's other Revit instances'). It stops short of routing the agent to siblings such as get_revit_operation_result for retrieving the outcome.

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