create_icon

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description adds meaningful behavioral context: it creates an editable bundle, preserves front-to-back ordering of groups/layers, and never overwrites existing names. This gives the agent expectations about z-order handling and name uniqueness that are not present in the annotations.

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 terse, purposeful sentences with no filler. The primary action is front-loaded, and the ordering and no-overwrite behaviors each earn their place without redundancy.

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 has a complex nested spec and no output schema, yet the description doesn't state what the tool returns on success or what happens on name collision (error versus silent no-op). The schema covers structural details, and the description adds ordering and uniqueness guidance, but the missing result/error contract leaves an important gap for an agent.

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?

With 0% schema description coverage, the description must compensate for parameter semantics. It does add value by clarifying that layers come from SVG or PNG and that groups/layers are ordered front-to-back, and by implying name uniqueness. However, it does not explain other top-level spec fields like background, platform, or darkBackground, nor how to choose between svg/pngBase64, so compensation is only partial.

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 uses a specific verb ('Create'), resource ('.icon bundle'), and input source ('static SVG or PNG layers'), making the core action clear. The '.icon bundle' and 'editable native' phrasing distinguish it from read/list/update/render siblings, though it does not explicitly name an alternative tool.

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 provides no explicit when-to-use guidance or alternatives. 'Never overwrites an existing name' implies a constraint, but it does not state that update_icon should be used for modifying existing icons, or when to prefer list_icons/read_icon. The agent must infer usage from the tool name.

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