volume-import

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Import an OpenVDB volume file'—it doesn't explain whether this creates a new object, overwrites existing data, requires certain permissions, or what happens on failure. The sparse description fails to illuminate side effects or post-conditions.

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, front-loaded sentence with no fluff. It efficiently communicates the core purpose without redundancy, earning high marks for conciseness.

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 the lack of an output schema and annotations, the description should explain the resulting state or relation to other volume tools (e.g., whether it creates a volume object that can be listed by 'volume-list'). It only states the action, omitting crucial context about the import's effects, making it incomplete for an LLM agent to safely invoke.

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%, so the description must compensate. It does not elaborate on the 'name' or 'path' parameters beyond what is obvious from their titles. For a simple import, the path is self-explanatory, but the description adds no extra value to parameter understanding, leaving the agent to infer usage.

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 the specific action 'Import an OpenVDB volume file', which clearly distinguishes this tool from siblings like 'volume-create_empty' and 'io-import'. The verb 'import' and the resource 'OpenVDB volume file' are precise and 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 provides no guidance on when to use this tool vs alternatives (e.g., when creating an empty volume vs importing a file). There is no mention of prerequisites, exclusions, or alternative tools, so the agent is left without context for selection.

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