Vulcan System & Project Inventory

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

Annotation already declares readOnlyHint=true, so safety is covered; the description adds the meaningful context that operations require a live connection to Maptek Vulcan Desktop and that project_info enumerates seven specific artifact categories. It does not describe failure behavior when Vulcan is not running, which would have pushed this higher.

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 summary sentence is front-loaded and the three bullets are terse and scannable, with file extensions inline where they add information. Slight redundancy between the 'Master tool' sentence and the bullet list, but nothing that wastes real space.

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?

With no output schema, the description is responsible for conveying return contents, and it does so by naming the file types project_info returns and what ping/capabilities report. Small gap: no indication of response shape or error/connection-failure output, but the operational picture is clear enough 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?

Schema coverage is 0% and the enum alone only gives action names, so the description carries the load — and it does, explaining the concrete meaning and output scope of each of the three enum values. Only the default behavior of 'action' (defaulting to project_info) is left unmentioned.

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?

Each action is described with a specific verb and resource (ping = check live connection, project_info = list block models/triangulations/DBs, capabilities = inspect Python modules), so an agent knows exactly what the tool does. The 'Master tool for Vulcan connectivity... inventory... SDK capabilities' framing also signals it is the umbrella entry point rather than one of the artifact-specific siblings, though it never names those siblings explicitly.

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 implies when each mode applies, but there is no explicit guidance on when to pick this tool versus vulcan_block_model, vulcan_triangulation, vulcan_design, and the rest. No prerequisites (e.g., 'requires Vulcan Desktop running') or exclusions are stated up front, leaving routing to inference.

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