screenshot_cell

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

No annotations are provided, so the description carries the full burden. It says 'Capture a screenshot' but does not disclose whether it's read-only, if any side effects occur, or what the return format is. For a screenshot tool, likely read-only, but not stated.

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 includes an 'Args' section, but it covers only one of four parameters, making it less efficient. It could be more structured to include all parameters or output details.

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 4 parameters, no output schema, and no annotations, the description is incomplete. It doesn't describe the return value (e.g., image path or data), how the screenshot is delivered, or the purpose of optional parameters like use_rasterize.

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. The 'Args' section explains only the required parameter 'cell_id' ('The cell object ID to screenshot'). Other parameters (notebook, session_id, use_rasterize) have no descriptions in schema or description, leaving them undocumented.

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 it captures a screenshot of a cell's content and output, using specific verb and resource. It distinguishes from sibling tools like screenshot_notebook (whole notebook) and inspect_graphics (graphics inspection). However, it doesn't explicitly differentiate from rasterize_expression.

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 context ('Useful for seeing plots, graphics, or formatted mathematical output') but does not provide when-not to use or alternatives among siblings. Implied usage is adequate but not explicit.

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