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

Annotations already cover the key safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false). The description adds useful context that storage keys are omitted and variant status is included, but it does not explain pagination behavior despite the cursor parameter.

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 two tight sentences with the core purpose front-loaded and no wasted wording. It is appropriately sized for a simple list tool.

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?

Given zero schema description coverage and no output schema, the description should explain the required appId, the cursor-based pagination behavior, and the shape of returned metadata. It only briefly notes storage-key omission and variant status, leaving important calling details incomplete.

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 0%, so the schema provides no semantic guidance for appId or cursor. The description does not explain either parameter, leaving the agent without information about app scoping or pagination.

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 states a specific read action ('Read screenshot/icon metadata and variant status') and clearly identifies the resource. It does not differentiate this tool from related siblings such as list_asset_formats, so it falls short of a 5.

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?

It gives no explicit guidance on when to use this tool versus alternatives, and it does not mention prerequisites or exclusions. The use case is only implied by the description.

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