Set Active Layer

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

Annotations already disclose destructiveHint=true and readOnlyHint=false, so the agent knows this is a state-changing write. The description adds minimal behavioral context beyond that—no mention of side effects on subsequent operations or selection—but it is not misleading.

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, front-loaded sentence with no unnecessary words. It delivers the action, the target, and an example in under 15 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?

The tool is simple with one parameter and has an output schema, so the description is fully adequate. It states what the tool does, gives examples, and annotations cover the safety profile; no additional context is needed.

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 schema fully documents the single parameter 'layer' (100% coverage), but the description adds concrete examples (F.Cu, B.Cu) that clarify valid input values, going beyond the schema's bare definition.

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 'set the currently active PCB layer by name' with examples (F.Cu, B.Cu), using a specific verb and resource. It distinguishes itself from siblings like add_layer (creating layers) and get_layer_list (listing layers).

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 the tool is used to switch the active layer, but it does not explicitly state when to use it versus alternatives, nor does it mention exclusions or prerequisites. Usage context is self-evident from the purpose but not explicitly articulated.

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