set_selection

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

No annotations provided. The description does not clarify whether selection replaces or adds to existing selection, or how invalid node IDs are handled. The behavioral trait of replacing current selection is implied but not stated.

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?

Single sentence, front-loaded with the core action. No wasted words, though it could be slightly expanded for transparency without becoming verbose.

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 tool with complete schema, the description is adequate but lacks details on selection mode (replace vs. add), behavior with out-of-scope nodeIds, and return value. No output schema exists, so description could mention return state.

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 100%, so baseline is 3. The description adds 'scroll viewport to them' for the zoomToFit parameter, but this is already clear from the schema. No additional semantic value beyond 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?

Description clearly states the verb 'select' and resource 'nodes', and notes the optional viewport scrolling. It distinguishes from sibling tools like 'get_selection' (read) and 'select_all_by_type' (filter-based).

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 explicit guidance on when to use this tool versus alternatives like 'get_selection' or 'select_all_by_type'. The description does not mention context or prerequisites.

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