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

Annotations already declare this is a non-readonly, non-idempotent, non-destructive, closed-world creation. The description adds only that icons are built-in and monoline. It says nothing about where the icon lands (current artboard?), what happens on repeat calls given idempotentHint=false, or how size/color defaults behave.

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?

A single tight sentence with the key constraint front-loaded and no wasted words. It is efficient, though the brevity borders on under-specification rather than disciplined conciseness.

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?

For an 8-parameter mutation tool with no output schema and zero schema descriptions, this is well short of what an agent needs — coordinate semantics, sizing units, and placement behavior are all missing. Only the icon-name lookup path is covered.

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 0% across 8 parameters, so the description carries the full burden and mostly fails. It only clarifies the 'icon' parameter by directing the agent to docs {components} for valid names; x, y, name, size, color, artboard, and stroke_width remain entirely undocumented (units, defaults, artboard vs. absolute coordinates).

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 gives a concrete verb ('Draw') and a specific resource ('built-in monoline icon'), which separates it from generic siblings like create_shapes, create_path, and draw_svg. It stops short of explicitly naming those alternatives, but the 'built-in monoline' qualifier does real disambiguating work.

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?

Usage is only implied: the parenthetical points to 'docs {components}' for icon names, which tells the agent how to pick a valid icon but not when to choose this tool over create_shapes, draw_svg, or generate_illustration. No exclusions or prerequisites are stated.

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