gh_set_toggle

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

Annotations already provide readOnlyHint=false, and the description's 'Set' matches that mutating behavior. However, the description adds no additional behavioral context such as whether the change persists, whether it triggers recomputation, or what happens if the component_id is invalid.

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 clear sentence with no filler. The core action is front-loaded and every word earns its place.

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 simple setter with an output schema, the action is clear, but the description omits how to identify the target component and any operational context. It is adequate but minimal.

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?

The phrase 'to true or false' explains the value parameter, but the required component_id parameter is not described at all. With 0% schema description coverage, the description must compensate but only partially does.

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 uses the specific verb 'Set' and names the resource 'Boolean Toggle component' with the target values 'true or false'. This clearly distinguishes it from sibling setters like gh_set_slider and gh_set_panel, which target different component types.

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 when-to-use or when-not-to-use guidance is given. The description does not mention alternatives such as gh_set_slider, gh_set_panel, or gh_set_parameter, nor does it state prerequisites like the component needing to exist in the Grasshopper document.

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