Drawing: Apply ISO Layer Set (bootstrap)

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

Annotations only declare destructiveHint=false; the description adds the genuinely useful behavioral traits of idempotency ('existing layers are not modified') and refusal semantics for unknown standards. This is real value beyond the structured fields, though it omits any note on scale of side effects or interaction with existing layer states.

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?

Three tight sentences that front-load the primary action, with no filler. The final sentence is slightly telegraphic ('Refused by name'), but nothing 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?

An output schema exists so return values need no explanation, and the description covers the action, idempotency guarantee, and input validation for a single-parameter tool. Nothing essential to correct invocation is missing.

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% and the enum values are already fully enumerated in the schema, so the baseline is 3. The description only restates the accepted standard names in its refusal sentence, adding validation semantics but no new per-value meaning beyond what the schema lists.

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?

Specific verb ('Bootstrap') plus a concrete resource ('full ISO-conformant layer set with correct colors and lineweights'), so the effect is unambiguous. It does not, however, differentiate itself from closely related siblings like template_apply_layers or drawing_apply_standard, which an agent could easily confuse it with.

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 bootstrap framing implies the usage context, and the refusal note scopes the valid inputs, but there is no explicit when-to-use versus template_apply_layers or drawing_apply_standard. Guidance is inferable rather than stated.

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