screenshot_notebook

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

With no annotations, the description carries full burden for behavioral disclosure. It mentions max_height prevents huge images, but does not disclose whether the tool modifies the notebook, requires a live kernel, has rate limits, or what the output format is beyond 'image'. The behavioral traits are poorly explained.

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 relatively short and front-loaded with the purpose. However, it includes an 'Args:' section that could be more efficiently integrated. It does not cover all parameters, so it is not as concise as it could be given the missing information. Adequate but not exemplary.

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 5 parameters, no output schema, and no annotations, the description is incomplete. It does not explain the return value in detail, missing parameters, or context about session management (session_id). The tool's behavior is under-specified for an agent to use effectively.

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 document all 5 parameters. It only explains notebook and max_height, missing session_id, use_rasterize, and wait_ms. The agent has no guidance on these three parameters, which severely limits correct usage.

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 captures a screenshot of an entire notebook window, which is distinct from the sibling tool screenshot_cell that likely captures a single cell. The verb 'Capture a screenshot' and resource 'entire notebook window' are specific and unambiguous.

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 does not provide guidance on when to use this tool versus alternatives like screenshot_cell. It also does not explain when to change default parameters or what prerequisites are needed (e.g., notebook must be open). There is no mention of when not to use it.

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