Focus Node

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

No annotations are provided, so the description carries full burden. It mentions centering viewport but is ambiguous about whether it changes the selection state (the verb 'select' could be misinterpreted). Missing details on behavior when nodeId is invalid or when no node is selected.

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 that conveys the core functionality without unnecessary words. Every part earns its place.

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?

Given no output schema and only two parameters, the description is incomplete. It omits critical details: what happens if no node is selected and nodeId is omitted, any side effects on canvas state, and the purpose of openInGrid. A user would need to infer or test missing behavior.

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%. The description explains that nodeId is optional and defaults to the selected node, adding some meaning. However, it does not explain the openInGrid parameter at all, leaving a significant gap.

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 ('Select a canvas node and center the viewport') and the resource. It distinguishes from siblings like 'get_selected_node' (only retrieval) and 'open_nodes_in_grid' (opens in grid), making the purpose specific.

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 provides one usage guideline: if nodeId is omitted, use the selected node. However, it does not explicitly state when to use this tool versus alternatives like 'get_selected_node' or 'open_nodes_in_grid'. The guidance is implied but lacks exclusions.

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