get_cop_vdb

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

No annotations are provided, so the description must carry the full burden. It only says 'Get', implying a read operation, but gives no detail about what 'VDB info' entails, whether it requires a specific node type, or any side effects/error behavior. Minimal disclosure.

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, efficient sentence that clearly identifies the tool's purpose with no wasted words. It is well-front-loaded, though it could arguably be too terse to be fully useful.

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 tool with one parameter and no output schema, the description is too thin. It does not explain what VDB info is returned, what format, or how to specify the path. Given the large set of sibling COP tools, more context is needed for correct invocation.

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 has one required 'path' parameter with no description, and schema description coverage is 0%. The description does not mention the parameter at all, so the agent gets no help understanding what path should refer to (COP node path vs VDB file path).

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 ('Get') and resource ('VDB info from a COP node'). It is clear and distinguishable from sibling COP tools like get_cop_info or get_cop_geometry, though it doesn't explicitly differentiate itself.

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?

Usage is implied: use when you need VDB information from a COP node. However, there is no guidance on when not to use it, prerequisites, or alternatives among the many sibling get_cop tools.

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