asset_save_inline_svg

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

Discloses that it writes multiple files to disk, validates SVG against original brief, and returns an AssetBundle. Provides sufficient behavioral detail given limited annotations (only openWorldHint=false).

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?

Front-loaded with purpose and usage trigger. Each sentence adds value, though the paragraph is dense and could be better structured with bullet points for clarity.

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?

Covers main workflow, validation, and output files. Could elaborate on optional parameters like brand_bundle and expected_text, and since there's no output schema, more details on return structure would help.

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?

Adds value beyond schema by mentioning validation details (viewBox, path count, etc.) and listing output files. Schema coverage is 60%, and description compensates with context on svg parameter and overall behavior.

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?

Clearly states it is a round-trip endpoint for inline_svg mode, explaining that it writes asset bundles from SVG text emitted in chat. Distinguishes itself from sibling tools (e.g., asset_generate_logo) by focusing on saving already generated 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?

Explicitly tells when to use: immediately after emitting SVG in chat. Does not explicitly state when not to use or list alternatives, but purpose and sibling names imply alternatives for different tasks.

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