Set Selection

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

No annotations are provided, but the description does not disclose whether this replaces the current selection, whether it is additive, or what the side effects are. It only restates the tool's name in different words, offering no behavioral detail beyond the schema's nodeIds parameter.

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 only four words, which is not overly verbose, but it is under-specified rather than effectively concise. It lacks the structural detail needed to be a useful tool description.

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?

With no annotations or output schema, the description fails to explain important context such as what the selection is used for, whether the tool has a return value, and how it relates to the editor state. Even though the parameter set is simple, the description is not complete enough.

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 the description does not mention nodeIds, its array format, or required status. The agent gets no extra semantic meaning beyond the raw 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?

The description 'Select specific nodes' uses a clear action verb ('select') and identifies the resource ('nodes'), and the word 'specific' implies nodeIds are used to target particular nodes. It distinguishes from the sibling 'get_selection' by indicating a setter rather than a getter, though it does not explicitly say it replaces the current 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?

No when-to-use guidance is provided. It does not tell the agent when to prefer set_selection over get_selection or find_nodes, nor mention any prerequisites or exclusions.

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