Add or remove multiple elements from the current selection in an Archicad project. Use it to adjust which elements are selected for subsequent commands.
Adds/removes a number of elements to/from the current selection. (Tapir, Element Commands)
| Name | Required | Description | Default |
|---|---|---|---|
| addElementsToSelection | No | ||
| removeElementsFromSelection | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation and non-reversible nature is known from structured data. The description adds almost nothing beyond restating add/remove: it does not say what happens with an empty selection, whether the selection is replaced or merged, or whether both parameters are applied in one order.
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?
One tight sentence, front-loaded with the action. The trailing parenthetical is dead weight that the description would be better without.
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?
A mutation tool with zero required parameters, 0% schema coverage, and no output schema leaves the caller guessing on the most basic points: mutual exclusivity of the two lists, ordering, and behavior with empty input. Annotations carry the safety signal, but the description should carry the rest and does not.
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% and both parameters are unannotated in the description. The tool name and prose imply an add/remove dichotomy, but nothing states that 'addElementsToSelection' and 'removeElementsFromSelection' are the two parameters, that they accept lists of element-id objects, or what happens when both are supplied – or neither, since both are optional.
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?
States a specific verb (adds/removes) and resource (elements to/from selection), and is distinguishable from the read-only sibling GetSelectedElements. The parenthetical '(Tapir, Element Commands)' is unexplained noise rather than clarification.
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?
No when-to-use or when-not-to-use guidance, and no mention of alternatives such as atomically replacing the selection versus incrementally modifying it. The sibling GetSelectedElements is closer to this tool than most of the listed names yet is never referenced.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.