svg_to_icon

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

With no annotations, the description must disclose side effects. It mentions the write is optional, but critically omits the 'similarity check' noted in the icons_dir parameter, whether existing files are overwritten, and the behavior of dry_run. This leaves the AI uncertain about the tool's safety and failure modes.

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 a single sentence that front-loads the core purpose and concisely notes the optional write behavior. There is no redundancy or filler; every word earns its place.

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 tool has no output schema and no annotations, but the description does not explain the return value (TSX code), the dry_run behavior, or the file write conditions (similarity check). These are significant gaps for a 4-parameter tool, leaving the AI without essential workflow details.

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?

All parameters have full schema descriptions, so the baseline is 3. The description adds little beyond the schema, only loosely tying the optional write to the icons_dir parameter without adding new meaning or usage nuance.

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 uses the specific verb 'Convert' and clearly identifies both the input ('raw SVG code') and output ('TSX icon component'). This differentiates it from the sibling tool extract_icons_from_figma, which handles Figma extraction.

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 context is clear: use this tool when you have raw SVG code that needs conversion to a TSX component. However, it does not explicitly mention alternatives or exclusion conditions, so it lacks the explicit guidance needed for a 5.

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