render_node_network

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

With no annotations, the description carries the behavioral burden. It states the core action and two parameters but does not disclose side effects like whether the network editor focus is permanently changed, whether existing files are overwritten, what happens on invalid node paths, or what the return value is.

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?

Front-loaded one-line purpose followed by required argument docs. No fluff and every sentence contributes necessary information. The structure is highly efficient for an agent.

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, together with the two arguments, adequately covers the action and argument purpose. However, without an output schema or annotations, it leaves unspecified the return behavior (e.g., does it return the saved file path, success status, or open the file?) and does not clear whether the network editor view is changed before capture.

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 0%, so the description must compensate. It minimally does so: 'node_path: Node path to focus on' and 'output_path: image file path' add meaning beyond the schema's plain string types, explaining what each parameter means and the role of each. It could add file format or path syntax details but provides sufficient meaning.

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?

States a specific verb and resource: 'Capture a screenshot of a node's network editor view.' It clearly distinguishes itself from siblings like capture_screenshot or render_viewport by specifying the network editor and the target node focus.

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 gives a clear context for what to do (capture a node's network editor view) but does not explicitly mention alternatives or when not to use it. It's implied, but no exclusions or sibling routing is provided.

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