ui_to_artifact

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It merely states the conversion action without indicating any side effects, required permissions, input handling details, or output format expectations. This leaves the agent without insight into tool behavior beyond the basic operation.

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, front-loaded sentence with no wasted words. It efficiently conveys the core purpose without unnecessary elaboration.

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, no annotations, and minimal parameter definitions, the description is insufficient for reliable tool invocation. It lacks critical information about input formats, parameter semantics, and expected results, making it incomplete for a tool with three required parameters.

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% for all three required parameters, and the description only partially compensates by listing artifact types that map to output_type. It gives no detail about what image_source accepts (e.g., URL, file path) and completely omits the role of 'prompt' in the conversion process.

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 a specific verb ('Convert') and resource ('UI screenshot') with clear output types ('artifact (code, prompt, spec or description)'). It is distinct from sibling tools like analyze_image or extract_text_from_screenshot, which focus on analysis or extraction rather than conversion.

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 a UI screenshot needs to be converted to an artifact, but it does not explicitly state when NOT to use it or suggest alternative tools. No exclusions or comparative context are provided, so guidance is only implicit.

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