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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds two non-obvious traits beyond that: the payload is size-bounded ('bounded base64') and the content should be treated as untrusted data, which is valuable behavioral/security context.

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, front-loaded sentences with zero filler. The read action comes first and the untrusted-data caveat immediately follows.

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 correctly explains the return value ('bounded base64') and adds the untrusted-data caveat. For a simple two-parameter read tool this is nearly complete; it only lacks disambiguation from sibling getters.

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 description is expected to compensate, but it says nothing about the two required parameters beyond what the names imply. The regex patterns in the schema carry most of the parameter meaning; the description contributes only the 'owned' framing.

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 verb and resource ('Read an owned brand asset') and adds the return format ('bounded base64'), which is more than a tautology. It does not, however, explicitly differentiate itself from close siblings like get_image_asset or get_brand_kit, leaving the agent to infer the 'brand asset' scope.

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 explicit when-to-use or when-not-to-use guidance, and none of the siblings (get_image_asset, get_brand_kit, set_brand_asset) are named as alternatives. The word 'owned' implies brand-kit scoping, but the agent gets no rule for choosing this tool over a similar getter.

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