reels_preview_asset

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value beyond that: it discloses that no mesh is loaded and no Blender process runs, and that results may legitimately be absent for source-only assets.

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?

Two tight sentences: the first front-loads the purpose, the second carries the usage caveat. No filler, no repetition of the title or schema.

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 single-parameter read tool with no output schema, the description covers when it is cheap and when data may be missing, but it never indicates what 'inspect' actually returns (image, URL, metadata), leaving the agent to guess the response shape.

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?

There is one required parameter, assetId, with 0% schema description coverage and only a regex pattern. The description compensates partially by tying it to 'one selected asset' and to prior search results, but it never states the expected identifier source or format explicitly.

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 a specific verb and resource: inspect the stored preview of one selected asset. The clause 'without loading its mesh or running Blender' implicitly contrasts it with heavier siblings such as reels_preview or reels_get_asset, but 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?

'Use after search' gives a sequencing hint, and 'previews may not exist for source-only assets' warns of a failure case. However, it never states when to prefer this over reels_preview or reels_get_asset, so the agent must infer the routing.

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