gh_cad_tracked_bake

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says the tool 'register and track' handles and mentions idempotency, but it does not clarify side effects, whether it modifies drawing state, how duplicate group_ids are handled, or what state the tool maintains. This is too thin for a stateful registration tool.

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 conveys the core purpose without filler. Every word contributes meaning, and the key concept of idempotent tracking is placed at the end for impact.

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?

Despite having an output schema, this is a stateful tracking tool with no annotations and zero parameter-level documentation. The description leaves out critical operational context: what group_id represents, how layer factors into baking, and how tracked handles enable idempotent updates. An agent would need more information to invoke it correctly in a real workflow.

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 must compensate. It gives some context for 'handles' by calling them 'baked AutoCAD entity handles', but it never explains the meaning of group_id, the role of layer, or how handles and group_id relate. Two of three parameters remain effectively undocumented.

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 names a specific action ('Register and track') and a concrete resource ('baked AutoCAD entity handles'), and ties it to a clear objective ('idempotent Grasshopper updates'). This distinguishes it from sibling gh_cad_* tools like gh_cad_build_pipeline or gh_cad_set_param_and_solve, whose names suggest different workflow steps.

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?

The phrase 'for idempotent Grasshopper updates' implies when the tool is relevant, but it does not explicitly state when to prefer this tool over alternatives or when not to use it. No sibling tools or exclusions are mentioned, so the guidance remains implicit rather than directive.

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