Set Entity Properties

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description aligns with those. The description adds the list of modifiable properties but does not disclose additional behavioral traits like revertability, validation behavior, or error conditions. With annotations covering safety, a score of 3 is appropriate.

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, clear sentence that immediately states the action and scope. No unnecessary words or filler, perfectly concise and front-loaded.

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 has 6 parameters (including required handle) and an output schema, the description is minimal. It does not mention that only provided properties are updated, or any side effects. However, with full schema descriptions and output schema existing, the description is adequate but not richly informative.

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 100%, meaning each parameter has a detailed description. The tool description merely lists the property names without adding any new meaning or context beyond what the schema already provides. Therefore, it meets the baseline for sufficient schema coverage but does not enhance understanding.

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 uses a specific verb ('Change') and resource ('properties of an entity'), and lists the exact properties (layer, color, linetype, lineweight, visibility). This clearly distinguishes it from sibling tools that modify geometry, create entities, or perform other operations.

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 provides no guidance on when to use this tool versus alternatives (e.g., entity_batch_modify, or other property-changing tools). It does not mention prerequisites, such as requiring the entity handle, 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.