assets_list_stock_pngs

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

With no annotations, the description carries the full burden of behavioral disclosure, yet it only enumerates content categories. It does not state that this is a read-only catalog listing, whether results are paginated/filtered, or what form the assets come back in for placement.

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 the verb first. It is somewhat adjective-heavy ('curated royalty-free', 'holographic') but nothing is padding in a way that harms selection.

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 zero-parameter read tool with no output schema, the description is minimally sufficient but omits how the listed assets connect to downstream tools such as element_add_stock or assets_load_from_path, which would help an agent complete the placement workflow.

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 tool takes zero parameters, so there is nothing for the description to explain; baseline 4 applies. The description correctly does not invent parameter guidance that doesn't exist.

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 verb 'Lists' plus the resource 'free transparent 3D cutout assets' states exactly what the tool returns. The enumerated content types (cutouts, holographic spheres, flares, photography) implicitly separate it from siblings like assets_list_stickers and assets_list_patterns, though no sibling is named.

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?

The description never says when to call this versus the other asset-listing siblings (assets_list_stickers, assets_list_patterns, assets_list_local) or elements_search. No prerequisites or workflow context is given beyond the vague phrase 'available for instant placement'.

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