Vulcan CAD Design Databases (.dgd.isis)

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose key effects such as rendering a layer onto the 3D screen, removing temporary CAD objects, and creating a polyline in a layer, but it omits permissions, reversibility, write scope, and response behavior for the mutation-like actions.

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 front-loaded and compact, using an action-oriented bullet list with no wasted prose. Each bullet contributes operation selection and parameter mapping information, making it easy to scan.

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 an 11-parameter, six-action tool with no annotations and no output schema, the description gives enough to select an action and identify the main parameters. It is not complete because it lacks return-value descriptions, safety and side-effect detail for mutating actions, and deeper semantics for several parameters.

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 usefully maps parameters to actions and distinguishes required from optional ones, e.g. 'layer_info' takes `dgd`, `layer`, optional `limit`, `offset`, and `create_polyline` takes `points`, optional `closed`, `colour`, `name`. It still does not explain value formats such as the structure of `points`, the meaning of `colour`, or the `load_method` enum values.

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 opens with a specific resource scope, 'Vulcan Design Databases (.dgd.isis), layers, and 3D CAD polylines,' and enumerates six concrete actions. Each action has a clear verb and target object, so an agent can understand the tool's purpose without opening the schema. It does not explicitly differentiate itself from sibling tools such as vulcan_canvas or vulcan_screenshot, which keeps it below 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?

The action list implicitly shows which operation to choose for listing databases, inspecting layers, loading layers, clearing temporary objects, and creating polylines. However, it gives no explicit when-to-use guidance versus sibling tools, no exclusions, and no prerequisites for the mutating or rendering actions.

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