Select Nodes

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

The description adds the side effect of focusing the viewport beyond what annotations provide (idempotentHint, openWorldHint). It does not contradict annotations. However, it does not mention that the previous selection is cleared.

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?

The description is a single well-crafted sentence that conveys the core action and side effect without any fluff. It front-loads the verb and resource.

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 selection tool with one parameter and an output schema, the description covers the main action and side effect. It could mention that it replaces prior selection, but given the tool's simplicity, it's sufficiently complete.

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%, and the description does not add extra meaning to the parameter beyond what the schema already describes (array of node IDs). The description's mention of focusing is a behavioral context, not parameter-specific.

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 tool sets the canvas selection to one or more nodes and focuses the viewport. The verb 'set' and resource 'canvas selection' are specific, and the action distinguishes this tool from many siblings that create, delete, or transform nodes.

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 implies usage when selection needs to be changed, but does not provide explicit guidance on when to use vs alternatives or when not to use it. No comparison with sibling tools like node_info or node_delete is made.

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