List a brand's assets

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

The description adds a critical operational detail: that the assets are provided 'each with a temporary signed URL.' This is a functional behavior crucial for any downstream call that relies on the asset, which is not captured in the static safety annotations.

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 highly efficient, combining the resource type, the scope of assets included, and the mechanism of delivery into a single, powerful statement without unnecessary 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?

It is highly complete for a resource listing tool. It explains exactly what the agent will receive and how that data should be utilized, fulfilling the role of a discovery tool perfectly.

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?

Since the schema description coverage is low (33%), the description compensates by defining what kind of assets are listed (uploaded vs. generated) and the purpose of the output (used for generation). This helps the agent understand the semantic nature of the identifiers.

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 tool clearly states it lists brand assets, distinguishing between 'uploaded brand assets' and 'previously generated brand creatives.' This makes its purpose specific and clearly differentiated from other brand retrieval tools in the sibling list.

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 provides excellent downstream usage guidelines by explicitly instructing the agent to 'Use those URLs as referenceImageUrls (image) or imageUrls (video)' for generation tasks. This defines the practical context in which the tool should be invoked.

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