set_entity_props

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

With no annotations, the description must disclose behavioral traits. It only notes that color uses ACI and 256 means ByLayer, and that it can act on a selection, but it does not mention required permissions, what happens to unspecified properties, how selection is determined, whether changes are reversible, or error behavior. This is a significant gap for a mutation 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?

The description is a single focused sentence, front-loads the action, and includes essential clarifying detail (ACI, ByLayer). No wasted words.

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 a simple tool, the missing parameter semantics, usage guidance, and behavioral details (due to no annotations) make the description incomplete for confident invocation. The output schema exists but doesn't excuse the absence of parameter explanations.

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. The description lists property names but does not explain the handle parameter, the meaning of default values (-1, empty strings), allowed values, or how partial updates work. Only color semantics (ACI, 256=ByLayer) are partially addressed.

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 clearly states the tool's function with a specific verb ('Change'), the resource ('properties of an entity (or selection)'), and enumerates the specific properties (layer, color with ACI, 256=ByLayer, linetype). This distinguishes it from sibling tools that set current defaults rather than modifying existing entities.

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 use for existing entities or selections, but does not explicitly state when to use this tool versus alternatives like set_current_layer or set_current_color. There are no exclusions or alternative guidance, so usage context is only implicit.

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