render_node_network

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

With no annotations, the description carries the full burden and discloses almost nothing beyond the one-line action. It does not say where the image is written when output_path is omitted, what format it is, whether the editor view is opened/changed as a side effect, or what the call returns (path, image data, or nothing).

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?

A single front-loaded sentence with no filler; nothing is redundant. It is efficient but so terse that the brevity comes at the cost of missing detail rather than through tight editing.

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?

For a two-parameter tool with no annotations and no output schema, the description leaves key questions open: the destination and format of the screenshot, the meaning of output_path, and what is returned. An agent cannot call this confidently beyond guessing at the argument names.

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 both parameters are bare titles. The description only implicitly explains node_path (the node whose network view is captured) and never mentions output_path or how it relates to the captured screenshot, so it fails to compensate for the coverage gap on the one optional parameter that changes behavior.

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 gives a specific verb and resource: capture a screenshot of a node's network editor view. It is clear what the tool produces, but it does not distinguish itself from close siblings such as capture_network_editor, render_viewport, or render_quad_view, so an agent cannot tell from the text alone which of those to pick.

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?

There is no when-to-use guidance at all: no statement of preconditions (e.g., the editor must be open or the node selected), no exclusions, and no reference to the alternatives that would do a similar capture. The agent must infer selection from the name alone.

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