import_asset

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

Goes well beyond the idempotentHint annotation by describing immutable revisions, partial batch failures, and the already_derived_from warning. These behaviors are not inferable from annotations alone and are critical for correct invocation.

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?

Four tightly packed sentences with no fluff. The core contract, parameter choice, and edge cases are all covered efficiently, and the most important information comes first.

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?

Covers the invocation contract, failure mode, idempotency, and duplicate-recipe warning. With an output schema present and annotations providing the safety profile, nothing essential is missing for correct use.

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 100%, so the schema already documents path/paths exclusivity, batch size, and failure behavior. The description reinforces exactly-one selection and batch failure semantics but adds little new parameter-specific information beyond the schema.

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 and resource: 'Import a local image file into the workspace and issue an immutable revision.' This clearly distinguishes it from sibling tools like export_asset by direction and outcome.

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?

Gives explicit guidance for the two mutually exclusive invocation modes (path vs paths) and explains batch failure behavior. It does not name alternative sibling tools explicitly, but the import/export contrast and local-file scope make the intended use clear.

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