render_node_network

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals key behaviors: homeAll() invocation, disk save behavior with QBuffer estimation for size_bytes, and response cap. However, it stops short of explicitly noting read-only nature or all side effects, though homeAll is disclosed.

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 three concise sentences with no wasted words. The main action is front-loaded, and each sentence provides meaningful implementation detail.

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 covers key operational aspects well but omits return value details (beyond size_bytes) and the meaning of ctx. The fit_contents type mismatch (string vs boolean) is not addressed. For a 4-param tool with no output schema, it is moderately complete but not fully self-sufficient.

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%, so the description must compensate. It explains node_path (must exist), fit_contents (triggers homeAll), and save_path (None means no disk write, uses QBuffer). ctx is not explained, leaving a 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 tool's function: locate the node's NetworkEditor pane, cd to the node, and take a screenshot. This specific verb+resource description distinguishes it from other rendering/screenshot tools like render_single_view or capture_pane_screenshot by focusing specifically on node network rendering.

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 operational guidelines (node_path must exist, fit_contents triggers homeAll, save_path=None behavior) but does not explicitly state when to use this tool versus alternatives. It doesn't mention 'use this instead of X' or provide exclusion criteria.

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