convert_figma_to_livewire

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

With no annotations, the description carries full responsibility for behavioral disclosure. It states only the high-level conversion action, but does not reveal side effects (e.g., file creation, overwrites), authentication requirements (e.g., Figma token), or any limitations. The agent has little insight into what occurs beyond the literal meaning of 'convert.'

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 concise sentence with zero fluff and immediately states the core action. While it is brief, it is efficiently worded and front-loaded, though it lacks any structural elements like prerequisites or parameter highlights.

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 tool's complexity (4 parameters, no output schema, no annotations), the description is severely incomplete. It does not explain what the conversion produces, whether it modifies files, how to handle authentication, or what the expected outcome is. The absence of behavioral and parameter details makes it inadequate for an agent to use reliably.

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 only 25%, so the description must compensate by explaining parameters. It does not mention figmaUrl, figmaToken, componentName, or layout, leaving the agent with no guidance on how to supply the necessary inputs. The schema itself only documents the optional token, so most parameters remain completely unexplained.

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 'Convert Figma design to Livewire component' uses a specific verb (Convert) and identifies both the input (Figma design) and output (Livewire component), clearly distinguishing it from sibling tools like convert_html_to_livewire or convert_image_to_livewire. The purpose is unambiguous and immediately actionable.

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 usage: when you have a Figma design and want a Livewire component. However, it does not explicitly state when to use this tool over alternatives, nor does it mention prerequisites like having a Figma URL or token. No exclusions or alternative tool references are provided, leaving selection partly inferred from the tool name.

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