Draw with SVG

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), the description adds valuable behavioral detail: the output is real editable paths, not a flattened image, and SVG can round-trip unchanged from extraction. It doesn't describe what destructive effects occur, but annotations already flag mutating behavior, so this is not a major 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?

Three focused sentences with no wasted words. The core transformation is front-loaded, followed by the use case and a round-trip nuance. Every sentence adds distinct value.

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 main behavior is clear, but with 7 parameters, no output schema, and minimal schema descriptions, the agent still lacks guidance on positioning, frame placement, scaling behavior, return value, and what destructive side effects might occur. Adequate for high-level understanding, but not fully complete for reliable invocation.

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 only 29%, and the description only reinforces the 'svg' parameter meaning. It does not explain x/y placement, parentId, name, height, or how scaling relates to width/height. With most parameters undocumented in the schema, the description should compensate but doesn't.

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 states a specific verb and resource: it turns SVG markup into editable Figma vectors, not an image. It explicitly differentiates itself from image insertion and other create tools by saying 'any shape the other create tools cannot express.'

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 clear usage context: use this for icons, logos, or shapes other create tools can't express, and it implicitly rules out image insertion by emphasizing these are editable vectors. It doesn't name specific sibling tools or state explicit when-not conditions, but the context is strong enough.

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