Isolate Elements

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

Annotations already establish the profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false). The description usefully adds that the effect is temporary/view-scoped and that it can be cleared, which the annotations do not convey. It stops short of saying whether the isolation persists in the saved file or affects other users' views.

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?

A single front-loaded sentence that states scope first and the reset caveat second, with no filler. Nothing could be removed without losing 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?

An output schema exists, so return values need no explanation, and the operation is conceptually simple. However, with an undocumented 'reset' parameter and no differentiation from the visibility-setting sibling, the definition leaves gaps an agent must guess through.

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 only 33%, so the description carries more burden than usual. It does explain element_ids and its empty-list reset behavior, but it never mentions the separate 'reset' boolean parameter, leaving an agent to wonder whether reset=true or an empty list is the intended way to clear isolation.

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 (isolate) and resource (element IDs) scoped to the active view, plus a reset behavior. It is clear on its own, but it never distinguishes itself from the closely related sibling revit_set_view_visibility, which an agent could easily confuse it with.

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?

There is no explicit when-to-use guidance, no preconditions (e.g. an active document/view must exist), and no named alternative. The word 'Temporarily' is the only signal that this is a transient visual state rather than a persistent change, leaving selection of this tool vs. set_view_visibility to inference.

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