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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely new context: output is size-bounded ('bounded base64') and the payload is untrusted data, a useful prompt-injection warning. It stops short of stating a size limit or failure modes.

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 short sentences, zero filler, with the read action and return form front-loaded before the security caveat. Nothing here could be removed without losing meaning.

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?

There is no output schema, so the description correctly describes the return value as bounded base64. For a single-parameter read with full annotation coverage that is nearly sufficient; only the asset_id semantics remain undocumented.

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?

With one parameter and 0% schema description coverage, the description carries the burden but only implies validity via 'owned image asset'. It does not explain the asset_id format (the schema's ^asset_[0-9a-f]{32}$ pattern) or that IDs must belong to the caller.

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 and resource ('Read an owned image asset') and even states the return form ('bounded base64'), so the agent knows exactly what it gets back. It does not name a sibling to differentiate from, notably get_brand_asset, 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?

'for reuse' implies the intended context but there is no explicit when-to-use, when-not-to-use, or alternative tool (e.g. get_brand_asset for brand-scoped assets). The word 'owned' hints at a scope constraint but the agent must infer it.

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