Set or clear the display color for a specific layer in a CAD drawing. Pass an empty string to remove the stored color.
Set or clear a layer display color. Pass an empty string to clear the stored color.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| color | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It does add useful behavioral context by disclosing the empty-string clear sentinel, which is not derivable from the schema. However, it omits whether the layer must already exist, error behavior, or permission requirements for this mutation.
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?
Two tight sentences with zero waste. The core action is front-loaded and the clearing hint follows immediately.
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 mutation tool with no annotations, no output schema, and 0% parameter description coverage, the description covers the key sentinel but leaves the name parameter and error/permission behavior unexplained. Adequate but with clear gaps.
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 coverage is 0%, so the description should compensate. It usefully explains the empty-string semantics of the color parameter, which the schema does not. But the name parameter (which layer this applies to, and whether it must exist) is left entirely 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?
States a specific verb and resource: sets or clears a layer's display color. This is clearly distinct from siblings like rename_layer, delete_layer, and set_entity_color. No explicit sibling routing, but the resource is unambiguous.
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 tells how to clear (empty string) but gives no guidance on when to use this versus set_entity_color or other layer-setting siblings. Usage is implied by the name rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.