viewer_select

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

Description notes that the tool replaces any previous selection, aligning with destructiveHint: true. Adds color distinction for second group. No contradiction with annotations.

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 sentences, front-loaded with primary function. Could be slightly more concise, but no waste.

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?

Covers key behaviors: highlighting, replacement, and obtaining IDs. Lacks details on error handling or behavior with invalid IDs. Output schema exists, so return value is not needed.

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%, so description compensates partially. Explains pnt_ids as group A and pnt_ids_b as optional second group with distinct color, but does not detail array format or behavior when both are empty.

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 clearly states the action ('highlights'), the resource ('elements in the open viewer'), and the identifier ('by pnt_id'). It distinguishes from sibling tools like viewer_clear and viewer_isolate by focusing on highlighting.

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?

Explicitly says to use viewer_list_clashes or viewer_get_properties to obtain pnt_ids, and describes optional second group. Lacks explicit when-not-to-use, but overall context is clear.

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