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

Annotations already establish this as a safe read (readOnlyHint=true, destructiveHint=false), so the description's job is to add return context — and it does, disclosing that each asset comes with a /_blob/<id> url and that total storage usage in bytes is included, which is valuable given there is no output schema. It omits pagination/result-size limits, which is a meaningful gap for a list tool.

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 front-loaded sentence with zero filler; the scope and the return content are packed in without redundancy.

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 one-parameter, read-only tool with annotations covering safety, the description supplies the missing return detail (blob URLs, storage total). What remains unstated — that `id` is the artifact id and how large result sets are handled — is minor but not trivial.

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?

The single `id` parameter has 0% schema description coverage, so the description must compensate. "Of an artifact" implies `id` identifies the artifact rather than an individual asset, but it never states this outright, leaving room for an agent to pass an asset id by mistake.

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 and resource ("List the uploaded assets of an artifact") and even names the return shape (blob url, storage usage), so an agent can immediately tell it apart from asset_delete or asset_upload_url. It stops short of naming a sibling explicitly, but the read-only listing scope is unambiguous.

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 statement of when to use this versus alternatives (e.g., to find asset ids before calling asset_delete) and no prerequisites or exclusions. The scope ("of an artifact") implies the context, but the agent must infer everything about selection.

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