Read current selection

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the output type (GUIDs) and temporal state ('currently selected') but does not discuss side effects, permissions, or rate limits; however, none are expected for a read-only getter.

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?

A single sentence that front-loads the verb and result ('Return the GUIDs') with no filler. Every word earns its place.

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 simple read-only getter with an output schema available and no required parameters, the description is largely sufficient. The only remaining gap is the undocumented optional port parameter, but the default null allows a correct invocation without further knowledge.

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?

The only parameter, 'port', has no schema description and a 0% schema description coverage, and the tool description does not explain its meaning or when to override the default null. The parameter is optional and has a default, so the gap is mitigated, but the description provides no compensation for the missing parameter semantics.

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 states a specific operation ('Return the GUIDs') on a clear resource ('elements currently selected in Archicad'), which unambiguously distinguishes it from sibling mutation tools like set_selection and clear_selection.

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 description makes the read-only context explicit: it is for retrieving the current selection, not modifying it. It does not name alternatives like set_selection/clear_selection, but the 'currently selected' scoping gives clear context without exclusions.

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