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

Annotations already declare this as a non-read-only, open-world, non-destructive write operation. The description adds only the 'No base64' input constraint and an optional build-copy behavior, while omitting idempotency semantics, overwrite behavior, and how URL/file imports are fetched or validated.

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 a single compact statement with the core import/reuse purpose and key constraint front-loaded. There is no filler or repetition, even though other dimensions are under-served.

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 12-parameter, nested-object write tool with no output schema and 0% schema description coverage, this description is far too thin. It omits required-parameter guidance and most input semantics, so an agent cannot confidently invoke it without reading the schema closely.

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% across 12 parameters, so the description must carry parameter meaning. It only alludes to asset_ids and a build copy, leaving urls, files, upload_ids, tags, rights, purpose, reference, workspace, idempotency_key, and overwrite unexplained.

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?

States a specific verb (Import) and resource (assets), plus two modes: reusing library asset_ids and optionally copying into a build. The 'No base64' constraint helps distinguish it from an upload path, though it does not name a specific sibling tool.

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 implies this tool is for importing or reusing asset IDs and not for base64 payloads, but it gives no explicit when-to-use/when-not guidance. It does not point to alternatives such as assets_upload_url, assets_list, or files_write, so the agent must infer the routing.

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