get_cop_vdb

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

No annotations are provided, so the description itself must disclose behavior. It only states that data is retrieved and documents the arguments; it does not mention whether reading the VDB triggers a cook, how it behaves for invalid node paths, or what exact data is returned.

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 short, front-loaded with the purpose, and contains no filler. The Args list is a reasonable structured reference for the two parameters.

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 simple two-parameter getter, the description is minimally viable: it identifies the target, the resource type, and both arguments, and the schema handles the default for output_index. However, the lack of return-format information, behavior notes, or alternative-tool guidance leaves clear gaps, especially with no annotations.

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 Args block must compensate. It does document both parameters—node_path as the COP node path and output_index as the output connector index—but the descriptions are terse and add only modest meaning beyond the schema titles.

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 clearly states a specific verb and resource: it gets VDB volumetric data from a COP node. The mention of 'VDB volumetric data distinguishes it from COP sibling tools like get_cop_geometry, get_cop_info, and get_cop_layer.

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 contains no guidance on when to use this tool versus the closely related COP getters, and no exclusions or alternative conditions are mentioned. An agent is left to infer the intended use solely from the tool name and the first sentence.

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