vegas_render

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

With no annotations, the description carries the full burden and does disclose two useful traits: the render is asynchronous (implying a poll-for-status workflow) and outputs never overwrite existing files (a non-destructive guarantee). It leaves unstated what 'guarded' actually enforces, permission requirements, whether cancel affects already-written output, or timeouts.

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?

A single dense sentence with no filler; the operation list is front-loaded and the non-overwrite guarantee is tacked on where it is most needed. Slightly crowded for four distinct actions, but nothing is wasted.

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 multi-action, asynchronous tool with an opaque nested params object, no annotations and no output schema, the description leaves critical gaps: no polling/status semantics, no param guidance, and no indication of what the guarded or cancel behaviors return. It gives a thin overview but not enough to invoke it confidently.

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 0% and the 'params' property is an opaque free-form object with no documentation of which keys start/status/cancel accept (renderer/template name, output path, etc.). The description only loosely echoes the action enum, so an agent has no basis for populating params correctly.

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 names the resources (renderers/templates) and the four operations (list, start, inspect/status, cancel) that map onto the action enum, so the agent can tell what the tool does. It stops short of distinguishing itself from siblings like vegas_status or vegas_capabilities, which appear to overlap with the 'status' and 'list' behaviors.

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?

It conveys that renders are asynchronous and 'guarded' but gives no when-to-use guidance: nothing says whether to poll with the status action here or with the sibling vegas_status, nor when other render paths should be preferred. The mode selection is left entirely to inference from the enum.

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