SetClassificationsOfElements

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

Annotations declare destructiveHint=true and readOnlyHint=false, flagging this as a mutating operation. The description adds real behavioral context beyond that: omitting classificationItemId clears an existing classification, and subelements are affected too. It doesn't state whether existing classifications are overwritten, whether the write is idempotent, or what errors occur for invalid ids.

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?

Three short sentences, front-loaded with the core action and the unclassify rule. The trailing '(Tapir, Classification Commands)' is metadata that adds little for an agent, but the overall length is appropriate.

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 destructive, no-output-schema mutation the description covers the essential unclassify trick and hierarchical scope, but omits return/error behavior and whether the whole input array is applied atomically. Adequate but with clear gaps given the destructive annotation.

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% at the parameter level, so the description must compensate; it does explain the omit-classificationItemId semantics, though that fact is also already documented on ClassificationId.classificationItemId in the nested schema. It says nothing about the elementId/classificationSystemId structure or that elementClassifications is an array of {elementId, classificationId} pairs, so the batch shape is left to the schema.

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 first sentence states a specific verb and resource ('Sets the classifications of elements'), and the remaining sentences add scope (subelements of hierarchical elements). It does not, however, distinguish itself from the sibling archicad_classify_elements or GetClassificationsOfElements, leaving the agent to infer which classification tool to call.

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?

It gives one genuinely useful conditional ('to set to unclassified, omit the classificationItemId field') and notes it works for subelements, but provides no guidance on when to prefer this tool over archicad_classify_elements or GetClassificationsOfElements, and no prerequisites or batch-size limits.

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