Open Nodes In Grid

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

Discloses the fallback behavior for omitted nodeIds, but no annotations exist. Does not clarify whether opening nodes replaces the grid or appends, or any side effects. Some transparency but incomplete.

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?

Two concise sentences, front-loaded with the main action, no unnecessary words.

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?

Adequate for a tool with one optional parameter and no output schema. Could clarify grid behavior (replace vs. append) but not essential for basic use.

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 schema has no descriptions (0% coverage), but the description adds meaning by explaining the fallback when nodeIds is omitted, which is beyond the schema's type definition.

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 (open) and resource (nodes in grid view), and distinguishes from siblings like 'focus_node' by specifying multiple nodes and grid view.

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 states when to use (to open nodes in grid view) and provides conditional behavior (if nodeIds omitted, use selected nodes). Does not specify when not to use, but context with sibling tools implies alternatives.

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