Get a creative-library asset

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

No annotations provided, so description carries full burden. It states the tool returns metadata and JSON content by default, implying read-only behavior, but does not disclose error handling, authentication requirements, or what 'metadata' includes. Adequate but not comprehensive.

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 sentences, no unnecessary words. The main action is front-loaded, and additional context is provided efficiently.

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?

Without an output schema, the description leaves the return format ambiguous (what does 'metadata' include?). It covers the main use case and differentiates from a key sibling, but lacks details on error handling and output structure.

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 coverage is 0%, so description must explain parameters. It hints at 'includeContent' by mentioning 'by default, the full JSON content' and explains the 'kind' values by detailing examples vs. design templates/canvas presets/shapes. However, 'slug' is not explained, and the relationship between parameters could be clearer.

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 clearly states the tool retrieves metadata and full JSON content for one creative-library item. It distinguishes from the sibling tool 'start_from_example' by specifying when to use each.

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?

Explicit guidance is provided: use this tool to fetch an asset, but when adapting an example, prefer 'start_from_example' which returns additional adaptation information. Also explains that design templates, canvas presets, and shapes are reusable modules that must be composed into a project.

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