autocad_set_layer_state

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so safety and repeatability are covered. The description adds genuinely new behavior: partial-update semantics ('Only given fields change') and the notable side effect that a missing layer is auto-created, which an agent could not infer from the annotations.

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 definition is front-loaded with the purpose, then a compact Args block and a one-line Returns. The Args block does restate some of what the schema already shows (the boolean meanings), but it is short enough that it costs little.

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?

An output schema exists, so the return-value sentence is a bonus rather than a necessity, and annotations already cover the mutation safety profile. The remaining omission is calling out the sibling hand-offs (create_layer/set_current_layer) for a tool that has several nearby layer operations.

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 reported as 0% at the top level, so the description must compensate, and it does: it names each field (name, frozen, locked, off), gives the boolean direction for each, states the auto-create behavior of name, and imposes the 'at least one' constraint that the schema does not express. Minor gap: no mention of the name pattern/length limits.

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 first sentence names a specific verb set and resource: freeze/thaw, lock/unlock, on/off for a layer. It is clearly distinguishable from create_layer/delete_layer by the state-change framing, but it never explicitly contrasts itself with autocad_set_current_layer, a closely related sibling, so it stops short of full sibling differentiation.

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?

Usage is only implied: 'give at least one' of frozen/locked/off tells the agent the call must include a state change, and 'auto-created if missing' hints at the create-then-configure workflow. There is no explicit when-to-use vs when-to-use-a-sibling guidance, e.g. versus autocad_create_layer or autocad_set_current_layer.

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