gh_bake_to_rhino

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

The description briefly indicates the tool writes (bakes) to the Rhino document, consistent with readOnlyHint=false. However, it lacks details on side effects (e.g., overwriting, layering behavior) or required document state.

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?

Single sentence accurately captures the tool's purpose with no wasted words. Front-loaded and easy to parse.

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?

With schema covering parameters and an output schema present, the description is minimally adequate. However, it omits context about what 'bake' entails (e.g., geometry conversion, layer handling) and does not warn about potential irreversible changes.

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 descriptions already clearly define both parameters: component_ids (required) and layer (optional with layer creation hint). The tool description adds no additional semantics 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?

Description clearly states the verb 'bake' and the resource 'output of one or more components into the active Rhino document.' It uniquely identifies the tool among siblings, as no other bake tool exists in the list.

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 on when to use this tool versus alternatives. The description does not mention prerequisites, excluded scenarios, or when not to use it.

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