Vulcan Envisage Colour Legends (.scd)

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that update automatically creates a .scd.bak backup and that restore consumes that backup, but it does not describe permission requirements, whether update is reversible beyond the backup, how partial failures are handled, or what list/inspect return. This is meaningful but incomplete disclosure for a mutating multi-action tool.

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 with the tool's domain and then uses a compact action list with parameter names in backticks. Every line corresponds to a distinct action, and there is no filler or repetition.

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 six-parameter master tool with no annotations and no output schema, the description covers the action model and the key update/backup behavior. It still leaves out return-value expectations for list and inspect, permission or environment prerequisites, and colour-value formats, which an agent would need to invoke update correctly.

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 does map parameters to actions reasonably well (scd for inspect/update/restore, scheme/table for update, preset or colours as alternatives), which is more than the schema alone provides. However, it does not define formats or accepted values for scd paths, table names, scheme names, or the colour string format, so significant semantics remain unexplained.

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 verb-and-resource statement ('reading and updating Maptek Envisage colour legends') and then enumerates four concrete actions, each with its own operation. That makes it clearly distinguishable from sibling tools such as vulcan_block_model or vulcan_design, which deal with different Vulcan artefacts.

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 gives strong implicit guidance: list for discovery, inspect for parsing, update for modification, restore for rollback. It does not explicitly state when not to use the tool or name alternatives, but for a domain-specific legend tool the action mapping is clear enough that an agent can select the right mode without further inference.

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