optimize_vector_svg

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

With no annotations, the description carries the behavioral disclosure burden. It explains the core transformations and the cost, which is useful, but it does not describe the output format, whether the operation is purely functional, or how the payment requirement affects execution. Some behavioral context is present, but important details are missing.

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 one compact sentence followed by a cost note. It is front-loaded with the core behavior and includes no filler, making it easy to parse and act on.

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?

Given the lack of an output schema and annotations, the description should clarify what the tool returns after optimizing, e.g., an optimized SVG string. It also mentions a cost but does not state whether paymentSignature is required for execution. These gaps make it slightly incomplete for an agent to call with full confidence.

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 100%, so the baseline is 3. The description adds meaning by indicating the payload contains SVG content and by specifying the exact cost for the paymentSignature parameter. This helps an agent understand what the parameters are for beyond the generic schema text.

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 specific actions: strips bloated XML, cleans SVG nodes, and converts paths for particular use cases. This clearly identifies the tool as an SVG optimizer and distinguishes it from sibling transformation tools like convert_svg_to_png or generate_svg_sparkline.

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 names concrete contexts for use: direct cutting, sublimation, and high-performance web graphics. It does not explicitly mention alternatives or exclusions, but the intended use cases are clear enough for an agent to route requests appropriately.

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