design_create_lockup

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

No annotations are provided, so the description carries the full behavioral burden. It implies a layer is created but says nothing about where the layer lands, whether an existing lockup is replaced, what is returned, or whether the sketch must already be open/selected.

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?

Two compact sentences with the core purpose front-loaded. The second sentence largely restates the schema default for variant, a small redundancy but not enough to call it bloated.

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 9 parameters, zero annotations, and no output schema, the description is thinner than the tool's complexity warrants. Positioning, color, and font parameters are fully documented in schema, but nothing explains the outcome of the call or prerequisites.

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 100% with sensible defaults and an enum for variant, so the schema does the heavy lifting. The description adds no meaning beyond it, merely restating that a mark is an SVG icon and a wordmark is text.

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 ('Create an identity lockup layer') and specifies the composition (mark SVG + wordmark text). It does not distinguish itself from the closely related sibling design_set_lockup_variant, which an agent could easily confuse for the same job.

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?

No statement of when to use this versus alternatives such as design_set_lockup_variant or design_create_symbol. The only usage-like information is the default variant behavior, which is already implicit in the schema default.

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