editor_set_selection

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

With no annotations provided, the description carries the full burden of disclosing side effects or state changes. It simply states the action without mentioning that selection mutates editor state, whether permissions are required, or how the optional property/value parameters affect behavior.

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, front-loaded sentence with no wasted words. However, it is so brief that it may be under-specified for a tool with three parameters, but conciseness itself is well handled.

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?

The description fails to explain the purpose of the optional property and value parameters, does not clarify return values or side effects, and omits any interaction with sibling tools. For a tool with three parameters and no output schema, this is insufficiently 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?

The input schema provides descriptions for all three parameters (node_path, property, value), achieving 100% coverage. The description itself adds no extra semantic meaning beyond what the schema already states, so the baseline score of 3 applies.

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 uses a clear verb and resource: 'Select node in editor.' It distinguishes itself from the sibling tool editor_get_selection, but it omits any mention of the optional property and value parameters, which could indicate a broader function beyond simple 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 guidance is provided about when to use this tool relative to alternatives like editor_get_selection or editor_set_node_properties. There are no prerequisites, exclusions, or contextual hints beyond the implied action of selecting a node.

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