gh_cad_sync_dynamic_block

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 only says 'Drive', without stating whether this mutates the drawing, requires an existing dynamic block, how the sync behaves, or what side effects occur. This is a significant transparency gap for a tool that likely modifies block 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?

The description is a single concise sentence with no filler or redundant phrasing. It is front-loaded with the core action and resource, though additional structured detail would have improved it without harming conciseness.

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 complexity—a nested properties object, zero schema coverage, no annotations, and an output schema—the description is too sparse. It omits preconditions, property formatting, return behavior, and how Grasshopper definitions map to block properties, leaving an agent with significant ambiguity.

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%, and the description does not explain the 'block_name' parameter or the structure of the 'properties' object. It offers only a conceptual hint that properties relate to AutoCAD dynamic blocks and Grasshopper parameter definitions, but it does not describe value formats, mapping semantics, or required keys.

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 ('Drive'), target ('AutoCAD dynamic block properties'), and mechanism ('via Grasshopper parameter definitions'), which distinguishes it from general CAD drawing tools. However, 'Drive' is somewhat vague—it does not clarify whether this reads, writes, or synchronizes properties—so it stops short of a 5.

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 description implies this tool is for controlling dynamic block properties through Grasshopper parameter definitions, but it gives no explicit when-to-use guidance, no exclusions, and no mention of alternatives like gh_cad_set_param_and_solve. The usage scenario is inferable but not explicitly stated.

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