get_cop_vdb

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

No annotations are provided, so the description carries the full burden. It does not disclose the return format of the VDB data, whether the node must be cooked first, whether output_index selects a specific volume, or any error/permission behavior. Only the retrieval direction is implied by the verb 'Get'.

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?

Short and front-loaded with the core purpose in the first sentence. The Args block largely duplicates schema titles, but overall it is tight and free of padding.

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?

No output schema and no annotations means the description must explain what an agent receives and how to interpret it. It says nothing about the structure of the returned volumetric data or how output_index maps to connectors, leaving a significant gap for a data-retrieval tool.

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. Instead 'Path to the COP node' and 'Output connector index' essentially restate the schema titles 'Node Path' and 'Output Index', adding no syntax, format, or meaning beyond them.

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: retrieve VDB volumetric data from a COP node. It is meaningfully distinguishable from siblings like get_cop_geometry and get_cop_layer by naming the 'VDB volumetric' payload. It stops short of explicitly contrasting itself with those siblings, so not a 5.

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?

There is no indication of when to call this versus get_cop_info, get_cop_geometry, or get_cop_layer, which all read COP content. No prerequisites (e.g., node must be cooked) or exclusion conditions are given.

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