List textures

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

With no annotations, the description must carry the behavioral burden. It usefully discloses what each texture record contains (size, UV resolution, layers, saved state), which establishes this as a non-destructive read, but it says nothing about the cost or side effects of requesting embedded data, or about result size/pagination.

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?

One front-loaded sentence with no filler, and the resource is stated before the payload detail. It is appropriately sized for a simple list tool, though the space spent enumerating return fields arguably belonged to the parameter.

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 one-parameter, no-output-schema listing tool the description is nearly sufficient — it conveys the record shape — but with no annotations and no output schema the agent still cannot tell what include_data_url does or how large the response can get.

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% and the sole parameter, include_data_url, is not mentioned anywhere in the description even though it materially changes the response (embedding full image data). With only one optional boolean, the omission is the single biggest gap in the definition.

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 names a specific verb and resource ('List the project textures') and even enumerates the fields returned (size, UV resolution, layers, saved state). It is clearly distinguishable from mutation siblings like bb_create_texture or bb_delete_texture, but it never contrasts itself with the other read-oriented listers (bb_list_elements, bb_list_animations), so it stops short of full sibling differentiation.

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 when-to-use or when-not-to-use guidance and no named alternative. The agent can infer it is a read-only listing from the verb, but nothing tells it when this is preferable to bb_project_info or a targeted query.

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