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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, and the phrase 'without spawning it into the scene' is consistent with that safety profile, adding useful confirmation that no scene mutation occurs. However, it says nothing about what is returned (image bytes, URL, format) or whether rendering has cost/latency implications, which it could given no output schema exists.

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 tight sentence with zero filler, leading with the action and ending with the key constraint. Efficient and well front-loaded, though the terseness is also what leaves parameters and output unaddressed.

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 four-parameter rendering tool with no output schema, an agent still doesn't know how the preview is delivered (inline image, file path, URL) or what width/height mean. The core purpose is clear, but the description is not complete enough for confident invocation.

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 50%: 'as' is heavily documented in-schema, but 'width' and 'height' have no descriptions at all, and the tool description never mentions them or the 'asset' argument. Units, defaults, and aspect behavior for width/height are left entirely undocumented, so the description fails to compensate for the coverage gap.

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?

States a specific verb (Render), a concrete resource (preview image of an asset), and a scope qualifier (without spawning it into the scene). The qualifier implicitly distinguishes it from spawn/play siblings like 'play', though no sibling is named explicitly.

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?

Usage is only implied: use this when you want to inspect an asset visually without adding it to the scene. There is no explicit when-to-use framing, no prerequisites, and no named alternative for the case where the agent does want to instance the asset.

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