Draw Original UI Icon

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 discloses only that output is 'local' (a filesystem write) and that the caller should verify the rendering; it says nothing about overwrite behavior, whether the SVG is returned or only written, what permission or directory assumptions apply, or how failures surface. For an unannotated file-writing tool this is a significant disclosure gap.

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 sentences, front-loaded with the core action and artifact, with the disambiguation and verification note packed into the second. No waste.

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 input schema is rich and self-documenting, and the description covers the essential 'author primitives, not a prompt' mental model. However, with no annotations and no output schema, the agent gets no information on what the tool returns, what the file layout looks like beyond the schema's dir default, or what 'verify the rendered result' concretely entails. Adequate but with clear gaps for a tool that writes to disk.

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%, so defaults, ranges, the 24x24 coordinate system and the primitive enum are all already documented in structured data. The description's enumeration of primitives merely restates the enum and adds no semantics beyond the schema. Baseline 3 applies.

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 artifact: 'Produce a local custom SVG icon from structured ... primitives'. This clearly separates it from retrieval siblings like find_icons/get_icon by implying net-new creation, though it never names them. The 'Not text-to-image generation' clause sharpens the boundary against a different class of tool, giving an agent enough to select it.

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?

It gives one explicit exclusion ('Not text-to-image generation') and one usage instruction ('verify the rendered result'), but never says when to call this versus find_icons, get_icon, or make_asset. The implied rule — use this when you must author an original icon from vector primitives rather than look one up — is left for the agent to infer.

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