viznoir

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

With no annotations provided, the description carries the full burden. It effectively discloses behavioral traits: it produces images (output behavior), details rendering features (auto-camera, lighting, post-processing), and lists quality presets with specific resolutions and effects. However, it does not mention performance implications, file size, or error handling.

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 well-structured with a clear overview, bullet-pointed features, quality presets, and a detailed parameter list. It is appropriately sized for a complex tool, though the parameter section is lengthy; every sentence adds value, but some redundancy exists (e.g., repeating effects in presets).

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 complex tool with 19 parameters, 0% schema coverage, and no output schema, the description is highly complete. It covers purpose, features, quality options, and detailed parameter semantics. The only gap is lack of output format details (e.g., image type, size limits), but given the tool's name and context, this is minor.

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?

Given 0% schema description coverage, the description compensates fully by explaining all 19 parameters in the 'Args' section. Each parameter is clearly defined with examples, ranges, and defaults (e.g., 'colormap: Color map preset (e.g., "Cool to Warm", "Viridis")'), adding essential meaning beyond the bare schema.

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's purpose: 'Cinematic-quality rendering' with specific features like auto-framing, 3-point lighting, SSAO, and PBR. It distinguishes itself from sibling tools like 'render' or 'preview_3d' by emphasizing high-quality, publication-ready output with advanced visual effects.

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 through quality presets (e.g., 'draft' for fast preview, 'publication' for clean lighting), but does not explicitly state when to use this tool versus alternatives like 'render' or 'preview_3d'. It provides context on different quality levels but lacks direct comparison or exclusion criteria.

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