List available 3D icons and illustrations

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

No annotations are provided, so the description carries the full burden. It uses 'Returns' and 'fixed' which imply a read-only, deterministic operation with no side effects. This is sufficient for a simple listing tool, though it does not explicitly state read-only or describe any error conditions.

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, efficient sentence that front-loads the main output (icon names) and specifies the grouping and special case (outro scene). No wasted words.

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 no-parameter, no-output-schema tool, the description adequately conveys what is returned: icon names grouped by category and illustration names for outro. It does not specify the exact data structure (e.g., list vs map), but given the simplicity, an agent can reasonably infer the expected response. The absence of output schema is offset by the clear enumeration of content.

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?

There are zero parameters, so the schema covers everything vacuously. The description does not need to explain parameters, and the baseline for 0-param tools is 4. It adds no redundant parameter information.

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 exactly what the tool returns: fixed 3D icon names grouped by category and flat illustration names for the 'outro' scene. It clearly identifies the resource (assets) and differentiates from siblings like list_components (components) and render_video (video rendering) without needing to open schemas.

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 makes the purpose clear but does not explicitly state when to use this tool versus alternatives like list_components or render_video. The usage context is implied by the content type, but there is no explicit when-to-use or when-not-to-use guidance.

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