Generate an image from a text prompt (for a slide)

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

Annotations indicate it is not read-only and not destructive. The description adds that it consumes AI credits and stores images as workspace attachments, providing helpful behavioral context beyond annotations.

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 slightly long but well-structured, front-loading the primary action and usage context. Each sentence adds value, though it could be trimmed slightly.

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 description covers the return value structure, how to use the result in slide images, and prompt tips. It lacks mention of error conditions or file size limits, but for basic usage it is complete.

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 three parameters have descriptions in the schema (100% coverage). The description adds valuable tips for the `prompt` parameter (e.g., clean, flat illustration, colors, no text) and explains the role of `nodeId` (permission-checked) and `workspace` (default 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?

The description clearly states the tool generates an image from a text prompt using AI, stores it as a workspace attachment, and returns a URL for use in slides. It distinguishes itself from the sibling tool `rootr_remove_image_background` by focusing on generation for presentation visuals.

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 explicitly says 'Use this when building a Rootr presentation' and provides detailed prompt tips (e.g., 'no text', specify colors). It does not explicitly exclude alternative uses, but the context is sufficiently clear.

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