import_nvbench

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

The annotations are all false and provide no behavioral safety profile, so the description carries the full burden. It discloses the parse-first import order, the whitelist of provider-referenced sidecars, and the byte-length verification bound to declared_size * 4. This is substantive beyond the structured fields, though it could have mentioned failure behavior or atomic-import rollback semantics.

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 main purpose is front-loaded in the first sentence, and the following details about sidecar discovery and size verification are essential and non-redundant. Every sentence adds meaningful information without fluff or repetition.

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?

Given that an output schema exists, return values need not be described. The description adequately covers the import scope, sidecar selection rule, and verification constraint. It is slightly incomplete in not addressing source_root or sensitivity handling, but those are partially inferable from their enums and the operation is otherwise well specified.

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 only 50%; path and expected_sha256 have schema descriptions, but sensitivity and source_root are only defined by enums/defaults. The description does not explain how sensitivity, source_root, or expected_sha256 influence the import, so it fails to compensate for the half of parameters that lack schema-level descriptions.

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 an NVBench JSON and its provider-declared sidecars as one atomic bundle.' It clearly distinguishes this from generic import tools by emphasizing the NVBench-specific payload and the sidecar grouping. The additional restriction about only importing referenced sidecar files sharpens the resource scope further.

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 clearly implies the use case: importing NVBench JSON output along with its referenced sidecars. However, it never names alternatives such as extract_nvbench, import_artifact, or qualify_artifact_import, and it does not explicitly state when this tool should be preferred over them. The routing guidance is therefore implied rather than explicit.

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