Check which Veida image models can be run without signing in and find the page for each. Filter by text-to-image, image-to-image, or any scene.
List the image models Veida serves, which of them a signed-out caller can run, and the page a human can run each one on.
| Name | Required | Description | Default |
|---|---|---|---|
| scene | No | any |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral burden and does a solid job: it discloses the tool's return content (models, signed-out accessibility, human-facing page). It does not mention output format, ordering, or error behavior, but for a read-only listing tool this is reasonably transparent.
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 main action and lists the key distinctions in parallel structure. Every part adds value, with no filler or repetition.
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 captures the core purpose and return value well, but it omits the 'scene' parameter's effect and offers no guidance on how to combine this tool with siblings like free_tier_limits. For a simple read-only tool with one optional parameter, this is adequate but not fully 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?
The schema has 0% description coverage, yet the description never mentions the 'scene' parameter or how it affects the results. The enum values (text-to-image, image-to-image, any) and default are visible, but the description adds no semantic meaning to help the agent decide how to pass this parameter.
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 a specific verb and resource: 'List the image models Veida serves.' It also clarifies the output dimensions (which models are available to signed-out callers and which page each runs on), which distinguishes it from siblings like generate_image and browse_tools without needing to read the schema.
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 when the tool is appropriate: when a caller needs to know available models, access restrictions for signed-out callers, or the page for each model. It does not explicitly name alternatives or when not to use it, but the context is clear enough for an agent to select this tool over the listed siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.