skill

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only says 'load' without explaining side effects, state changes, permissions, or safety implications. The agent cannot tell if this is a read-only or mutating operation.

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 two concise sentences plus an example, with no wasted words. The purpose is front-loaded, and the structure is clear and easy to parse.

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 loads a skill but does not specify what happens afterward—whether it returns skill contents, executes actions, or modifies state. With no output schema and no annotations, this is a significant omission for a tool that likely has consequences.

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 input schema already provides a detailed description for the 'name' parameter (100% coverage). The tool description adds only an example ('restyle'), which is helpful but not essential. Baseline of 3 is appropriate as the schema does the heavy lifting.

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 that the tool loads a procedural skill consisting of a workflow, tool sequence, and anti-patterns. The verb 'load' is specific and distinguishes it from sibling tools that perform direct actions like 'set_fill' or 'create_component'.

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 explicitly advises using this tool 'FIRST' when adjusting an existing canvas or before creating a new design if a matching skill exists. This provides clear context for when to use it, though it does not name specific alternative tools.

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