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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds a genuine behavioral nuance beyond that: text assets return their text content while non-text assets apparently do not, which tells the agent to expect a conditional payload.

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 sentence that front-loads what is returned and lists the fields in a compact, scannable run. Every clause carries information; there is no filler.

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?

With no output schema, the description carries the burden of describing the return value, and it does so reasonably well by enumerating fields and the text-content special case. It is slightly thin on edge behavior (missing asset, truncation of large text), but for a two-parameter read tool with full annotation coverage it is nearly 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?

Schema description coverage is 100%: assetId is documented as coming from content, node outputs, or upload completion, and workspaceId as coming from fuzz_list_workspaces/fuzz_create_workspace. The description adds nothing about the parameters, which is acceptable when the schema already does the work.

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 gives a specific verb (Returns) plus the resource (a stored asset) and enumerates exactly which fields come back: name, MIME type, size, dimensions, and text content for text assets. It is unambiguous about what the tool does, though it never names or contrasts the obvious siblings fuzz_download_asset and fuzz_preview_assets.

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?

There is no when-to-use or when-not-to-use guidance. The presence of fuzz_download_asset and fuzz_preview_assets as siblings makes the choice non-obvious, and the description does nothing to route the agent between retrieving metadata versus downloading or previewing the asset.

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