autocad_set_current_layer

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

Annotations carry the safety profile (idempotentHint=true, destructiveHint=false). The description adds two non-obvious behaviors: auto-creation of missing layers and that the effect is on the live UI. It does not disclose what happens on invalid names despite the schema pattern, but the additions exceed the annotation baseline.

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-loads the action in the first sentence with the auto-create caveat, then documents args/return concisely; the Args/Returns block is somewhat redundant given the schema.

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?

With an output schema present, the return-value summary is appropriately brief; the main missing piece is failure behavior for invalid layer names or a UI-less connection, minor for a single-param 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?

Schema coverage is 0%, so the description's 'name (str): layer to make current' is the only semantic hint beyond the JSON schema's type and pattern constraints, which is thin but for a single-parameter tool this is adequate.

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 ('Make a layer current'), distinguishes from sibling autocad_create_layer and autocad_set_layer_state, and notes the auto-creation caveat.

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 'Mainly affects a live AutoCAD UI' phrase hints at a live-document precondition, but there is no explicit when-to-use vs autocad_set_layer_state or autocad_create_layer, and no stated exclusions or error conditions.

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