gh_bake_to_rhino

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

The annotation readOnlyHint=false already signals mutation, and the description adds that output is written into the active Rhino document. It does not disclose side effects such as whether existing baked objects are replaced or whether a GH definition must be running, but the core write behavior is clear.

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 to identifying the action, object, and destination.

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 bake operation, the description plus schema is mostly sufficient, but it omits practical context about obtaining component IDs and ensuring the components have computed output before baking. The available output schema may cover return values, so that gap is minor.

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 description does not explain parameters, but the schema's nested properties define component_ids ('Components whose output to bake') and layer ('Target Rhino layer (created if absent)'), so the schema carries the semantic load. The description adds no additional parameter value beyond what the schema already provides.

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 gives a clear verb ('bake'), resource ('output of one or more components'), and destination ('active Rhino document'), so an agent can tell what the tool does. It does not explicitly say 'Grasshopper' or distinguish this from sibling tools like gh_run or gh_data_tree_get, so it misses full sibling differentiation.

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 provided about when to use this tool versus alternatives, nor are prerequisites mentioned, such as having a Grasshopper definition open or needing component IDs from gh_component_list. Usage is only implied by the word 'bake'.

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