Import Threat Model Archive

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

With no annotations provided, the description fully carries the behavioral transparency burden. It discloses that the operation is mutating, requires write access, assigns a fresh model_id on each import, auto-suffixes title collisions, is otherwise non-destructive, and that restored models arrive UNVERIFIED. This is unusually rich and actionable.

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 front-loaded with the core action and mutation effect, and the longer unverified-model paragraph is purposeful rather than filler. Still, the final paragraph is somewhat verbose and could be tightened without losing meaning, so it is not maximally concise.

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?

The description covers purpose, usage, prerequisites, safety, idempotence, collision behavior, and post-import verification state, and the output schema presumably handles return-value details. The main gap is the unexplained server_version parameter, and the lack of annotations means the description must do all the work, which it almost does.

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?

The schema already documents envelope and workspace_id, and the description adds useful semantics: the envelope comes from export_report and the target workspace must be writable. However, the required server_version parameter is never explained anywhere in the description or schema, so a necessary input remains opaque.

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 a specific verb and resource: 'Import a JSON audit archive' into a target workspace, and clearly distinguishes this from sibling import tools by emphasizing it creates a NEW threat model. It also ties the archive format to export_report (scope="model", format="archive"), making the tool's scope unambiguous.

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 explicitly says when to use this tool: 'Use to move or clone a model between workspaces or across instances,' and even names the required companion export operation. It does not explicitly list exclusions or compare against other import siblings such as import_controls or import_compliance_framework, but the intended context is clear.

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