Edit SVG

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

No annotations provided; description discloses it writes back to svg_path or output_path and returns an updated summary, but lacks detail on overwrite behavior, permissions, or side effects beyond the basic write action.

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?

Single sentence of 26 words, efficiently lists key operations. Could be improved with bullet points or clearer separation of operations.

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?

With no output schema and 3 parameters, description omits details on operation requirements, error handling, and expected summary content. Incomplete for a tool editing files.

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 coverage is 0%; description lists operation types but adds no detail on parameter formats (e.g., color as string, translate as array). Does not compensate for missing schema descriptions.

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 clearly states the tool edits an SVG by applying structured operations (setFill, setStroke, etc.) and mentions writing back to a file. It distinguishes from siblings that convert, import, inspect, optimize, or render SVGs.

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 implies use when SVG edits are needed but does not explicitly state when to use this tool versus alternatives or provide when-not-to-use guidance.

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