autocad_create_layer

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the bar is lower. The description still adds real value beyond them: the create-or-update branch, and the 'warning' emitted when the requested linetype is unavailable with fallback to CONTINUOUS.

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?

Front-loaded with the core behavior in the first sentence, then structured Args/Returns blocks. Slightly redundant to include a Returns section when an output schema exists, but no sentence is wasted.

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 an output schema exists, the return description is optional, and the description covers the key non-obvious facts (upsert status, linetype fallback warning). It omits any statement about required document/session context, which is the one gap for a state-mutating layer tool.

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?

The Args block restates name/color/linetype and their defaults (7, CONTINUOUS), but the visible input schema documents each of these more richly (pattern, min/max, ACI color mapping, fallback rule). The description adds little meaning the schema does not already carry.

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+resource ('Create a layer') and adds the upsert nuance ('or update its color/linetype if it already exists'), which distinguishes it from autocad_delete_layer / autocad_set_layer_state. It never names a sibling explicitly, so routing depends on the agent inferring from names.

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?

There is no when-to-use, prerequisite, or when-not-to guidance. Nothing tells the agent whether a drawing must be open first, or when to prefer this over set_layer_state / set_current_layer. The upsert clause describes behavior, not selection criteria.

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