gh_preview_toggle

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

The readOnlyHint=false annotation already signals mutation, and the description adds that preview state changes for selected components or all. However, it does not explain whether 'toggle' means flip current state or set it according to the 'enabled' parameter, nor does it describe any side effects or requirements such as needing an open Grasshopper document.

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 filler. Every word contributes meaning: the action, the target resource, the optional scope, and the 'all' case are all conveyed efficiently.

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?

Given the tool's low complexity and existing output schema, the description is mostly adequate, but it leaves ambiguity around the enabled parameter's role and the exact way to target all components. It also does not clarify that this is Grasshopper-specific preview behavior, which could matter given the large sibling toolset.

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 carries the burden. It does add meaning by linking 'on/off' to the enabled boolean and 'a list of components (or all)' to component_ids. However, it does not explicitly explain that null component_ids means all, or that enabled determines the target state rather than toggling based on current state.

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 a specific action ('Toggle preview on/off') applied to a specific resource ('a list of components (or all)'). This distinguishes it from sibling tools like rhino_render_preview or gh_bake_to_rhino because it focuses on Grasshopper component preview state.

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?

No guidance is given about when to use this tool rather than alternatives. There is no mention of prerequisites, exclusions, or comparison with similar preview/visibility tools like rhino_viewport_preview or gh_component_list. The intended context is only implied by the name and the word 'components.'

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