generate_screen_from_text

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the basic outcome of generating a new screen. It does not reveal whether the screen is persisted, whether it replaces an existing screen, whether it is asynchronous, or what side effects occur in the project.

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, putting the verb and outcome first. It is appropriately concise, though slightly under-specified for the number of sibling tools and lack of annotations.

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?

For a generation tool with no annotations and no output schema, the description is too thin to fully guide an agent. It omits behavioral context, expected output, and any caveats about the generation process, leaving the agent to infer important details from the schema alone.

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 100%, so the parameters are already fully documented in the schema. The description adds minimal value by clarifying the prompt is a 'text description of the desired UI,' but it does not explain deviceType or projectId beyond what the schema already provides.

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 clear action ('Generates') and resource ('a new screen') with a specific method ('from a text prompt'). It is understandable and distinguishable from list/get/edit screens, though it does not explicitly contrast with sibling generation tools like batch_generate_screens or generate_from_template.

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?

No guidance is provided about when to use this tool versus the many related siblings such as generate_from_template, batch_generate_screens, or edit_screens. There are no exclusions, prerequisites, or alternative conditions mentioned.

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