create_svg_node

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals that the tool creates a new vector graphic, but it does not mention whether the node is inserted into the current selection, how parentId affects placement, what happens if the SVG is invalid, or whether anything is returned. For a create tool with no annotation safety signals, more behavioral context is needed.

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 short sentences with no redundancy. The core mechanism ('from SVG markup') is front-loaded, and the use-case sentence is compact and informative. Every sentence contributes 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 schema is rich with 100% parameter coverage and the purpose is clear, so the basics are covered. Still, with no annotations and no output schema, the description does not explain insertion behavior, return value, or how this tool relates to sibling creation tools. Some important operational context is missing.

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 the input schema already documents every parameter. The description adds only 'SVG markup' context for the svg parameter and does not explain width, height, name, or parentId beyond what the schema already provides. Baseline 3 is appropriate since the schema handles parameter semantics.

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 clear action and resource: 'Create a vector graphic from SVG markup.' This is specific enough to understand what the tool does. However, it does not explicitly distinguish this from sibling tools like create_icon or create_vector, especially since it lists icons/logos/illustrations as use cases.

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 provides some usage context by saying 'Use for icons, logos, illustrations,' which tells the agent common scenarios. However, it gives no guidance on when to prefer create_icon or create_vector instead, and no exclusions or alternatives are mentioned. The usage guidance is implied rather than explicit.

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